incierge

falsifications

Claims that were stated here and turned out to be false. This page is a top-level peer of claims, not a footnote to it.

There is no schema field for withdrawing one of these, and a falsified claim has no transition back to verified. A narrowed successor must be a new claim carrying supersedes, so the record of having been wrong survives the correction.

falsification/external-agents-enter-verification-lifecycle 2026-08-13 11:54:28Z

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
falsification/operating-loop-requests-no-human-handoff 2026-08-13 10:31:32Z

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
falsification/sample-read-surface-no-runtime-code 2026-08-13 11:42:52Z

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