The coverage gate
PROC-AUDITOR-COVERAGE is a locked, always-on Process-integrity exit condition: every material surface must be covered. It makes an unverified part of the project a visible failure rather than a silent blind spot.
A surface belongs to one of three classes — code, harness, or doc — and the gate decides coverage one class at a time.
When a surface is covered
| Surface class | Covered when |
|---|---|
code |
an active auditor runs in that module |
harness |
the required harness is activated or resolved by an attestation |
doc |
a file under |
The engine collects the code, harness, and doc surfaces and evaluates each against its rule. A project with no surfaces passes the gate GREEN.
When it reds
Any surface with no covering auditor, harness, or doc file makes the gate RED. The message names each gap — for example uncovered: web (node). The gate stays red until every named surface is covered or waived.
Closing a gap
A gap is closed by covering the surface, not by adopting a check from a catalogue. Author an auditor for a code surface (delegating to its ecosystem’s toolchain, then reviewed adversarially and approved), activate or attest the required harness, or add a docs/ file that names the id. Add a React app under web/ and the gate reds until a web auditor exists.
Waiving
A surface that genuinely needs no coverage can be marked intentionally unaudited, with a recorded reason; the gate then skips it. See Project surface coverage for how surfaces are detected and waived.