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 |
| 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 |
3 processes of 3 — pagination by twenty. The Links column counts the related pages, which brings the most central processes of the journey to the top.