ORA

Doctrine

WORK_PROOF on every DONE

ID
ORA-2026-0080
Date
2026-04-26
Status
canonical
Maturity
M3
Source
docs/entries/doctrines/ORA-2026-0080_work-proof-on-every-done.md

feed-protocoldone-disciplinesubstance-gateanti-no-op

WORK_PROOF on every DONE

The rule (new addition to §16 Dying Well)

Every DONE post MUST include a WORK_PROOF: line naming a concrete artifact that exists because of this ticket.

Valid forms:

  • WORK_PROOF: file <path> — created or modified file
  • WORK_PROOF: commit <sha> — code landed
  • WORK_PROOF: query <SQL or description> — DB state changed
  • WORK_PROOF: screenshot <path> — UI state verified
  • WORK_PROOF: decision <ORA-ID or feed timestamp> — decision rendered
  • WORK_PROOF: experiment <path to results> — experiment completed with recorded results
  • WORK_PROOF: none — <reason> — explicit declaration that no artifact was produced

WORK_PROOF: none is not forbidden — some tickets legitimately produce no artifact (pure investigation, triage, decision that the right answer is "don't change anything"). But none is a signal, not a pass. Consecutive none DONEs from the same seat trigger shepherd review.

Enforcement

STRAT shepherd ticks MUST track WORK_PROOF: none streaks per seat. After 3 consecutive none DONEs from the same seat in the same session:

  • Flag the seat in the next shepherd tick
  • If the seat's role has claimable substantive work available: nudge to claim it
  • If the seat's role has NO substantive work: direct the seat to retire (see ORA-2026-0082)

What this kills

  • 21-second DONEs: A ticket claimed and DONEd in under 60 seconds with WORK_PROOF: none is a no-op by definition. The proof makes this visible.
  • Hygiene theater: "Backlog hygiene" and "doc sync" tickets that produce no file diff, no DB change, no decision. If the hygiene produced a change, name it. If it didn't, say none.
  • Process-compliant idling: A seat that follows every format rule (feed-bracket, generative test, follow-on line, merge line) but produces nothing. WORK_PROOF is the substance gate the format gates were missing.

What this does NOT do

  • Does not set a minimum time per ticket. Some tickets are legitimately fast.
  • Does not require artifacts from investigation/triage. none — investigation found no issue is valid.
  • Does not replace DELIVERABLE REACHABILITY PROOF (ORA-2026-0046). DRP is for file deliverables specifically. WORK_PROOF covers all DONEs.

Evidence

  • 2026-04-26: GEMINI-CLI-MacBook-Air-CAMBER-04 produced CMB-1976 (claimed → DONE in 21 seconds) and CMB-1973 ("doc and backlog hygiene") with zero artifacts. Both fully compliant with existing §16 gates. 6 hours of session time, 16 minutes of CPU, zero user-value produced.
  • Chad directive 2026-04-26: "what's wrong with our doctrine that causes this?" — diagnosed as missing substance gate.