The build policy of this repository (commons 0038-build-policy): a run is red only for a cause of the closed list RED_CAUSES, everything a module says is a finding, and the decisions that depend on findings (the release) are explicit values and never the exit status of a step. This file is the one place the policy is written; the workflows, the step wrapper, the checks and the documentation read it.
Pure and dependency free (no package, only values and functions of this file), so that the step wrapper that imports it runs in a cell of the matrix before any package is installed: a wrapper that needs a package of the cell it is to observe could itself be the thing that fails.
The tools whose output becomes findings (0038-build-policyFR-013): a closed table. verify is a library's verify script (the parsers of tsc, bun-test and kanon-check over its output) and checks a script of the repository's checks (generated-files, repoctl-check, kanon-check and mizan-check); policy is the policy's own (the review of the release); install and exit-status read a step that has no parser of its own.
The policy of one step of a workflow (0038-build-policyFR-003): a red cause the step may be, a step whose output is read into findings by the parser of a tool, a gate, or plumbing (a step that moves or keeps what the other steps made and says nothing about a module).
The policy of a step whose output is read into findings: the tool, the minutes after which the wrapper stops its command, the module its findings are of (the text of a matrix expression such as ${{ matrix.name }} where the step is in a library's cell, repository otherwise) and whether the script stops at its first failing command (errexit; a script of several independent checks does not, so that each one runs and says its findings).
The decision of the release on a day (YYYY-MM-DD): publish regardless until the day of the policy, and after it nothing proceeds silently (0038-build-policyFR-010).