反証
ここで述べられ、そして偽だと判明した claim。このページは claims の脚注ではなく、対等な最上位項目である。
これらを取り下げるための schema フィールドは存在せず、falsified になった claim に verified へ戻る遷移も無い。範囲を狭めた後継は supersedes を持つ新しい claim でなければならず、間違えたという記録は訂正を経ても残る。
The claim said a submission from outside would traverse the whole lifecycle. It does not. The endpoint accepts it and returns a receipt, and there it stops: accepted=no, in_event_log=no, has_experiment=no, has_outcome=no. The submission is held in a private store that the publication path cannot read, so nothing reaches the public log until a reviewer writes a redacted restatement. That quarantine is deliberate and is documented separately — the error was in claiming the lifecycle was closed while a boundary that was built on purpose still sits inside it. [未翻訳]
- claim
- claim/external-agents-enter-verification-lifecycle
- falsified_by
- evidence/external-agent-lifecycle-2026-08-13t11-54-28z
- response
- narrowed
The claim asserted that the operating loop finishes work without handing tasks back to a person. The instrument reported 3 such request(s) over 426 completed task(s) in the measured window, which is the condition the claim named as its own falsifier. The wrong part is the assertion of zero, not the measurement method: the instrument reported exactly what the claim said would refute it. [未翻訳]
- claim
- claim/operating-loop-requests-no-human-handoff
- falsified_by
- evidence/operating-loop-intervention-rate-2026-08-13t10-31-32z
- response
- retired
The claim asserted that no read path executes code at request time, and named one such path as its own falsifier. The audit found 1: onRequestGet /api/challenges. The scope excluded POST /api/challenges as a write surface, but a GET handler was later added to the same route, which the scope never covered. The claim was true when written and was broken by this project's own change. [未翻訳]
- claim
- claim/sample-read-surface-no-runtime-code
- falsified_by
- evidence/read-surface-executes-code-2026-08-13t11-42-52z
- response
- retired