Factory
Open source / public proof
Inspect proof

Proof surface / verified locally 2026-09-28

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
[false-delivery] exit=1
GATE: BLOCKED
  state.open_questions[0] is blocking and unanswered: '[redacted blocking question 1]'
  state.open_questions[1] is blocking and unanswered: '[redacted blocking question 2]'
  state.open_questions[2] is blocking and unanswered: '[redacted blocking question 3]'
  state.open_questions[3] is blocking and unanswered: '[redacted blocking question 4]'
  state.open_questions[4] is blocking and unanswered: '[redacted blocking question 5]'
  ac-matrix.md row 'AC-1' has status 'partly met'; allowed: met, unrunnable, failed
  ac-matrix.md row 'AC-2' has status 'partly met'; allowed: met, unrunnable, failed
  terminal 'delivered' needs every acceptance criterion met; use 'delivered-with-gaps' and name each gap and its owner

Why this verdict

  1. Five blocking questions have no recorded answer.
  2. Two acceptance criteria use the invalid status partly met.
  3. 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 manifestfixture statecomplete gate output

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.

03
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
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

Read the gate-bug case study Inspect a complete Factory run