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