A problem MUST have one of four levels: fail, warn, pending (something not set up yet that waits on time or on someone else) and action (a step that is the person's to take); pending and action MUST NOT be failures, and MUST NOT be counted as warnings. A problem MAY carry a message, the phase it happened in, one fix, the raw text of a system error, its line in the log, and a stable code: E for a problem and P for what is pending, then upper-case words joined by dashes (E105-DISK, P000-WAITING); a program MAY give the code a problem carries where its raiser gave none, one for each level, and Headless MUST give one where the program gives none. Taken from: stolos 052-self-describing FR-001 and FR-004 (four states, stable codes E and P), 105-calm-output FR-009 (a generic code per level) and 099-engine-update (action is neither warning nor error).
Enforced (check): .github: cd commons/headless && bun run verify — suite/governance-problems.test.ts: a problem has one of four levels, holds only the fields given, and the counts are of its levels; suite/governance-problems.test.ts: a stable code is E or P then upper-case words, and each level has a generic code that a program may replace
Proved by: headless/suite/governance-problems.test.ts
Written in: headless/src/governance/problems.ts
Tests: passed: suite/governance-problems.test.ts a problem has one of four levels, holds only the fields given, and the counts are of its l; passed: suite/governance-problems.test.ts a stable code is E or P then upper-case words, and each level has a generic code that a pr
Cited by: governance/problems, Headless