Processes
7 processes described. 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 |
|---|---|---|---|
| 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 |
| Lint | service | concordance lint runs the same checks as the build pipeline on a single knowledge repository, before any site exists. In local scope it needs no network and writes nothing unless asked to fix. In global scope it reads the latest published model to check what one repository cannot see alone: links into other sources, frontmatter relations across sources and homonyms with the glossary; it never rebuilds the model. | 81 |
| Query | mixed | concordance query reads the model a build wrote and answers what it knows, without the site and without a source: the note an expression names, where it is used with file and line, what it is linked to and how sure the model is, the decisions and sessions among those links. The same command runs the search of the site with its ranking and facets, lists the entities, counts them, names the spaces and the domains, lists the recurring expressions nobody defined and where they were read, what changed and with what, the findings the build recorded, and where a phrase is written or spoken in the documents and the transcripts. It answers a person at a terminal and, in the same words, an agent that puts the answer in its context. | 73 |
| 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 |
| Release | human | How a version of the tool is cut and what it publishes: the npm packages under one shared version number and the preset, the container image tagged with the version and latest, a git tag v<major>.<minor>.<patch> on the main branch, a release whose notes are 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 the same version. Every form of one version names the same commit: the tag, the packages on npm, the image, the action, the component and the pre-commit hook. Versions follow semantic versioning; before 1.0.0 a minor version may break compatibility and says so, a patch never does. The release guide is the contract; the one decision that stays human is the merge of the version pull request, and the publications to the registries stay disabled until the maintainer enables them. | 34 |
| Publishing the wiki | service | The loop that keeps this wiki alive: a change in the glossary or in the specifications is linted where it is written, then the configuration repository rebuilds the site of the three repositories and publishes it. Nothing is copied from one repository to another and nothing is written into a content repository. Until the first release of the tool, every workflow builds the command line from a checkout of the tool's repository, the interim form of the pipelines the guide gives with the published package. | 30 |
| 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 |
7 processes of 7 — pagination by twenty. The Links column counts the related pages, which brings the most central processes of the journey to the top.