Proof surface / verified locally 2026-09-21

A delivery claim should survive inspection.

Run the same gate against an unsupported claim, a supported claim, and a contradiction the gate itself once missed.

3 verified-local claims13 mapped artifacts3 executable cases

The specimens

Same gate. Three different records.

Switch between the committed gate receipts. The core claims, artifacts, limits, and before-and-after case remain visible below without client-side JavaScript.

Recorded stateNot deliveredexit=1 · GATE: BLOCKED

5 unanswered2 invalid

terminalfactory gate

$ bash proof/terminal-gate/run.sh
checking manifest .......... ok
checking delivery answers .. 5 unanswered
checking reported checks ... 2 invalid

GATE: BLOCKED
delivery_status=not_delivered
exit=1

Why this verdict

Five blocking questions have no recorded answer.
Two acceptance criteria use the invalid status partly met.
The requested delivered state is unsupported by the record.

What blocked means

The evidence is insufficient. Factory refuses to call the work delivered and names what is missing.

Receiptsproof manifest fixture state case study

Machine-readable claims

The manifest names the proof—and its limits.

These cards are rendered from the public manifest that maps each statement to exact repository artifacts.

verified-local

Factory rejects delivered when five blocking questions are unanswered and two acceptance criteria use the invalid status partly met.

Boundary: The fixture is a redacted reconstruction of the historical failure shape, not the original private run.

3 mapped artifacts

proof/terminal-gate/false-delivery/state.json
proof/terminal-gate/false-delivery/ac-matrix.md
proof/terminal-gate/false-delivery/receipts.md

verified-local

The same terminal gate accepts delivered when every represented question is answered and every represented acceptance criterion is met.

Boundary: This proves the terminal gate accepts this fixture; it is not a complete multi-phase delivery run.

3 mapped artifacts

proof/terminal-gate/honest-delivery/state.json
proof/terminal-gate/honest-delivery/ac-matrix.md
proof/terminal-gate/honest-delivery/receipts.md

verified-local

Factory rejects a request to validate delivered when state.json already records blocked.

Boundary: The before/after case was reconstructed from repository history after the fix; it was not a Phase 0-6 Factory-orchestrated run.

7 mapped artifacts

proof/terminal-gate/mismatched-terminal/state.json
proof/terminal-gate/mismatched-terminal/ac-matrix.md
proof/terminal-gate/mismatched-terminal/receipts.md
proof/case-studies/terminal-state-mismatch/README.md
proof/case-studies/terminal-state-mismatch/before.txt
proof/case-studies/terminal-state-mismatch/after.txt
proof/case-studies/terminal-state-mismatch/regression-test.patch

Open proof/manifest.json Read exact gate output

The gate failed too

One contradiction. Before and after.

The old gate trusted the requested terminal without comparing it with the recorded state. The reconstructed regression is part of the product story.

Before / false pass

state.terminal: blocked
requested: delivered

GATE: PASS
exit=0

Baseline e0f8277

After / honest refusal

state.terminal: blocked
requested: delivered

GATE: BLOCKED
exit=1

Fixed by fd1cd03