A–Z index
1,019 words used in the documentation. 252 have a written page, the others exist through their uses alone.
Filters
B42 words
| Word | Type | First line of the page, or most cited passage | Pages |
|---|---|---|---|
| badge | no definition | “… grid of three regions. The left column is the tree of the space: an initials badge and the title of the source, leading to the page of the space, its folders b…” — Entity page | 6 |
| band | no definition | “…ash signature of 128 functions under a fixed seed; LSH banding, four rows per band, enumerates the candidate pairs, two signatures that share no band being neve…” — MinHash for twin resources | 2 |
| banding | no definition | “… shingles of five words, then to a MinHash signature under a fixed seed; LSH banding enumerates the candidate pairs, so that the full matrix of a corpus is neve…” — Twin resources review | 3 |
| banner | no definition | “…same template as a note, without the markdown and the declared properties: a banner says no note exists, three numbers give the occurrences, files and sources, …” — Keyword | 3 |
| bar | no definition | “…sktop; the text never shrinks, the two side regions give way. Under 700 px the bar keeps a menu button, a bordered square of 48 px, the mark, the site name cut …” — Entity page | 17 |
| base | no definition | “…it and the folder only reinforce a pair. A pair is founded by a declaration in the frontmatter, a shared base name, a title equal to a heading, or similar text.” — Twin resources review | 14 |
| base, components | no definition | “…and: search, mentions panel, mode switch. Four cascade layers: tokens, base, components, project. The project stylesheet is loaded last and wins by constructi…” — Theme override model | 4 |
| base, components, project | no definition | “… search, mentions panel, mode switch. Four cascade layers: tokens, base, components, project. The project stylesheet is loaded last and wins by construction. …” — Theme override model | 3 |
| BCP | no definition | “… comes as a pack shipped by a plugin. Each source selects its pack through its BCP 47 locale, which decides its comparison form, its stopwords, its word segment…” — Language pack | 4 |
| BCP 47 | no definition | “…omes as a pack shipped by a plugin. Each source selects its pack through its BCP 47 locale, which decides its comparison form, its stopwords, its word segmentat…” — Language pack | 4 |
| binaries | no definition | “… the changelog entries with the tarball of every package and the standalone binaries as assets, and the mirrors of the GitHub action and the GitLab component at…” — Release | 4 |
| bound | no definition | “…at PDF and nothing else, and the conversion: block of the configuration that bounds it: timeout_s (120) per document, max_size_mb (50) beyond which a file stays…” — Conversion | 4 |
| Bounded neighbourhood | Decision | Co-occurrence is accumulated per paragraph and never materialised as a full matrix. Only the fifty best neighbours of each node are kept, ranked by count then by identifier. | 0 |
| branch | no definition | “An author pushes a note to the main branch of the glossary or of the specifications, after the lint of the merge request.” — Publishing the wiki | 2 |
| breadcrumb | no definition | “…ree of the space of the page, the source it comes from. In the centre, the breadcrumb, the title, a line naming the type, the last change and the space, then th…” — Entity page | 15 |
| broken | no definition | “…and out of the link resolution, so that a link towards an excluded file is a broken link; concordance lint --no-gitignore reads the ignored files anyway, for th…” — Excluded file | 7 |
| Broken link | Business rule | A markdown link written in a note points to a file that does not exist in its source. The link is not recorded and the reader lands on nothing. | 39 |
| Browse | no definition | “…“publication treshold”", the search on the last segment of the address, and "Browse the spaces". Between the sentence and the exits, "Nearby addresses" lists th…” — Edge cases | 5 |
| browser | no definition | “…ers are set when the site is published and that the filtering happens in the browser, without a round trip; on a phone the column folds behind a "Filters" headi…” — Search | 20 |
| budget | no definition | “…e viewer. The specification named an interactive console for openapi contracts. It weighs more than the page budget, and it wants to call the api from the page.” — Contract import scope review | 15 |
| budget of 150 | no definition | “…lands for the interactive parts, content reachable without JavaScript. A budget of 150 kB per page, measured on every build. Theme override model · 2026-08-27…” — Theme override model | 3 |
| budget of 150 kB | no definition | “…nds for the interactive parts, content reachable without JavaScript. A budget of 150 kB per page, measured on every build. Theme override model · 2026-08-27 ·…” — Theme override model | 3 |
| Build | Term | One run of concordance build: it validates the configuration and the lock it names, fetches the sources, runs the inference chain and the checks, writes the model, the build log and one fragment per… | 82 |
| Build | Business object | One run of the build pipeline on a configuration: the sources it ingested with their commits, the model and the build log it wrote, and its summary. The summary counts the entities per type, the… | 213 |
| build and the linter | no definition | “…model and returns findings. Checks live in one registry shared by the build and the linter, so both report the same thing on the same repository. Each check has…” — Check | 3 |
| build error | no definition | “…e language of the interface, whose labels come from a message catalogue per locale, and the default locale of every source. A tag with no pack is a build error.” — Locale | 3 |
| build imported | no definition | “The block of the API page of an API whose contract the build imported. It shows the contract next to the note without copying anything into the markdown: what t…” — Contract viewer | 3 |
| build imports the operations | no definition | “Contracts: an API note declares its contract, the build imports the operations, each operation note absorbs the operation it names, and a purpose-built viewer r…” — Roadmap outline | 4 |
| Build log | Term | The file build.log.json the build writes next to the site: its summary (sources, files, entities per type, links per method, keyword pages and expressions under the threshold, twin resources, the… | 42 |
| Build pipeline | Process | concordance build chains its steps in a fixed order and produces one build. Each step is a pure function of the outputs of the previous ones and reports its anomalies as findings; no content anomaly… | 163 |
| build reports | no definition | “… the word is searchable but has no page. The threshold is configurable, and the build reports how many pages it generated and how many expressions it discarded.” — Keyword page threshold | 3 |
| build summary | no definition | “…t all; the publication threshold decides which of those become pages, and the build summary reports the pages generated and the expressions under the threshold.” — Publication threshold | 3 |
| build. A SARIF | no definition | “…e the notes are written, the same checks in the merge request and in the build, a SARIF log in the margin of the diff; the wiki keeps pace with the tool, every …” — Roadmap outline | 3 |
| build. A SARIF log | no definition | “…the notes are written, the same checks in the merge request and in the build, a SARIF log in the margin of the diff; the wiki keeps pace with the tool, every ch…” — Roadmap outline | 3 |
| build. Two builds | no definition | “…y recurring expression a keyword page, every doubt a finding in the build log, never a stopped build; two builds of unchanged sources give byte-identical files.” — Roadmap outline | 3 |
| built contract | no definition | “…call the API from the page. The contract of an API is shown by a purpose-built contract viewer, an island rendered from a JSON fragment of the contract, loaded …” — Contract import scope review | 3 |
| built contract viewer | no definition | “…l the API from the page. The contract of an API is shown by a purpose-built contract viewer, an island rendered from a JSON fragment of the contract, loaded on …” — Contract import scope review | 3 |
| built from the passages | no definition | “…ing that of the rows shown. The related pages are the mentions panel built from the passages of the decision itself, the pages its text cites, with the pages th…” — Decision page | 4 |
| built viewer | no definition | “…ct, the build imports the operations, each operation note absorbs the operation it names, and a purpose-built viewer renders the contract under the page budget.” — Roadmap outline | 3 |
| built viewer renders | no definition | “…ct, the build imports the operations, each operation note absorbs the operation it names, and a purpose-built viewer renders the contract under the page budget.” — Roadmap outline | 3 |
| bundle | no definition | “…ved as its static markup inside an element carrying its props, and one small bundle per island, named after a hash of its content, mounts the same component on …” — Slots, islands and layers | 10 |
| byte | no definition | “…son file in canonical order. Two builds on the same sources produce the same file byte for byte. The site is rendered from it without reading the sources again.” — Model | 14 |
Words without a definition sit in the index like the others, dotted, with the passage that uses them most in place of a definition. That is the working list of a glossary owner.