Ingestion
3 pages filed under Processes › ingestion. A process is a sequence of steps the business or the tool follows, with the roles, screens and rules each step involves.
| Process | Execution | First line | Links |
|---|---|---|---|
| Adding a language pack | human | A language is described by data, never by code: a folder holding pack.yaml (the name of the language, its apostrophes, its collation options, its plural suffix rules, validated by the language pack schema) and stopwords.txt. The engine ships en and fr; a regional variant such as fr-CA uses the pack of its language until a more specific one is registered; any other language comes as a pack shipped by a plugin, registered when the plugin loads, and a locale with no pack is a build error. Every source selects its pack through its BCP 47 locale, which decides its comparison form, its default stopwords, its word segmentation and the collation of its indexes. The architecture guide states the design. | 27 |
| Build pipeline | service | 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 stops the chain. Two builds on unchanged sources produce byte-identical files. | 163 |
| Onboarding a repository | mixed | The path from a folder of markdown files to a published wiki, and the one every new knowledge repository follows to join an existing wiki. The integrator does the declaration and the two settings a forge asks for; the build pipeline and the lint do the rest. On the golden corpus the whole path takes under thirty minutes, and the repository of the tool replays every command of it on each change so that the guide never promises a step that fails. | 41 |
3 ingestion of 3 — pagination by twenty. The Links column counts the related pages, which brings the most central ingestion of the journey to the top.