Gate: unit-complete
The spec has code, feature and test that realise it.
| Property | Value |
|---|---|
| Checker | unit-complete |
| Confronts | spec |
| Blocking by default — new project | yes |
| Blocking by default — existing project | no — informs |
How it measures
Section titled “How it measures”Confronts a spec of a GOVERNED layer against the simplest question of the unit: do the pieces that realize it exist? The code it specifies, the feature that covers it, and the test that proves it.
It exists because the relational gates FAIL OPEN by construction. Without a test linked, the feature↔test confrontation returns “nothing to confront yet” instead of failing; without code, the dependency one likewise. The side effect is grave: a lone spec, with no implementation at all, crosses ALL the gates and the pipeline concludes “can promote” — the green certifying work that does not exist.
This gate closes the hole from the positive side. Instead of asking “do the pieces match?” — which requires that they exist —, it asks “do the pieces exist?”.
Declaring it
Section titled “Declaring it”gates: - name: unit-complete on: [spec] check: unit-complete