Configuration
6 pages filed under Ingestion › configuration. A term is a word of the business with its definition, its aliases and the words it relates to.
| Term | aliases | First line | Links |
|---|---|---|---|
| Configuration | concordance.yaml, configuration file | The file concordance.yaml of the configuration repository, validated by the published configuration schema and read first by every command: its version, the project, the profile, the plugins, the applications, the domains, the privacy block, the sources, the staleness thresholds, the inference options, the conversion limits, the build block, the site options, the checks overrides and the lock. concordance validate-config prints one line per faulty key; concordance init writes a commented one. | 131 |
| Configuration repository | wiki repository, config repository | The repository that holds the configuration, the profile override, the theme, the stopword files, the lock and the pipeline that builds the site and publishes it, and no content: the notes stay in the knowledge repositories it declares as sources. Copying it is how a wiki of one's own starts. | 63 |
| Locale | BCP 47 tag, locale tag | The language of a source or of the project, written as a BCP 47 tag, en, fr, fr-CA. The locale of a source selects its language pack, the type prefixes of the profile for that language and the collation of its indexes; the locale of the project is the 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. | 81 |
| Lock | lock file | A versioned file in the configuration repository, concordance.lock.yaml, named by the lock key of the configuration, that records human decisions: accepted and rejected links, merged and separated twin resources, rejected candidate expressions, promoted emergent domains. The build reads it, validates it against the published lock schema and stops on a missing or invalid file as on a configuration error. It applies the rejected terms, compared on the normalised form of the language pack, so that a rejected expression has no candidate, no finding, no keyword page and no mark in the text, and the merged and separated pairs, a merged pair grouped under the criterion lock file whatever its score, a separated pair never reported, and the domains, a note the proposal reached filed under the domain of the integrator's choice unless a declaration files it already. The links are recorded, not read. The build log counts the decisions applied. Nothing is ever written into a knowledge repository. | 82 |
| Profile | meta-model, default profile | The YAML file that describes the meta-model: types, their attributes, the relations and the pairs of types they may join, the sections whose heading maps to a relation, the confidence scale, the display rules. The engine knows nothing else. A project profile is merged over the default one; adding a type never requires a code change. | 136 |
| Project | project block, wiki project | The wiki being built, as the project: block of the configuration declares it: its name, shown in the site; its locale, the language of the interface and the default locale of the sources; its theme, the theme file relative to the configuration, theme.yaml next to it when the key is absent; its edit_url, the pattern of the edit link with {source}, {path} and {commit} placeholders, derived from the forge of a GitHub or GitLab source when absent; and its contribute_url, the HTTPS address every call to action of the site leads to when no forge link can be built for it, "Propose a definition" or "Edit this page", which the site leaves out rather than shows inert when neither is known. The project locale, the project profile and the project stylesheet are the ones this block, the profile and the theme name. | 151 |
6 configuration of 6 — pagination by twenty. The Links column counts the related pages, which brings the most central configuration of the journey to the top.