A content anomaly (4 passages, no note) becomes a finding (note: Finding), never a crash (3 passages, no note). The build (note: Build) fails only when the configuration (note: Configuration) says so. Every check (note: Check) is a pure function in a registry (11 passages, no note) shared by the build and the linter (3 passages, no note), and a test enforces their parity (note: Linter and build parity).
Findings, not failures
Decision · Acceptedspecs/decisions/quality/findings-not-failures
Properties
- Status
- Accepted
- Decided on
- Session
- Contract import scope review
3 keys: the status and the date are authoritative.
See the neighbourhood map6 pages6Neighbourhood mapFindings, not failures
Neighbourhood map Findings, not failures
Distance1 hop
13 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- Linter and build parityBusiness ruleaffects1
- Build pipelineProcessaffects1
- LintProcessaffects1
- FindingBusiness objectaffects1
- BuildBusiness objectaffects1
- Contract import scope reviewMeetingis documented by1
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.