Gate: progress-honest
The plan’s progress file tells the truth about the disk.
| Property | Value |
|---|---|
| Checker | progress-honest |
| Confronts | plan |
| Blocking by default — new project | yes |
| Blocking by default — existing project | no — informs |
How it measures
Section titled “How it measures”The -progress.md is the only Anchors artifact that nothing confronted, and its exclusion
from the map is deliberate: it exists in order to CHANGE, and the gates that demand a
justification for change cannot reach it.
But “outside the map” turned into “outside any verification”, and the two are not the same thing. An item that cites a file PATH is trivially confrontable: the file exists, or it does not.
Measured in the reference project: when the 17 progress files were created, the checkbox
state was carried over from the plans — and the plans were out of date. The progress of
0002 claimed 6 open items with 7 of the 8 specs already on disk. FIVE items lied, and the
lie was transported faithfully.
The damage runs in two directions, and the second is worse: an open box with the file
already there produces rework — somebody redoes what is done. A ticked box with the file
absent declares a plan finished with work still to do, which is the same defect the explicit
Closes shut through another door.
A gate that only looks INSIDE the file never sees what is missing from it. That is the third direction, and it is how this gate once passed a plan that had just gained a seeded spec: the progress said the phase was over, and the next-card command moved on to another plan with work declared undone.
The gate is anchored on the PLAN — which IS in the map — and confronts its companion. That is the only way to reach a file that, by design, is not a node.
Declaring it
Section titled “Declaring it”gates: - name: progress-honest on: [plan] check: progress-honest