claim/external-agents-enter-verification-lifecycle

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. [未翻訳]

falsified_by

evidence/external-agent-lifecycle-2026-08-13t11-54-28z

response

narrowed

A conforming challenge submitted from outside traverses all four stages: accepted, recorded in the public log, connected to an experiment, and reaching evidence or a falsification. [未翻訳]

A conforming challenge was submitted to https://incierge.jp from an external client. HTTP 429. Stages: accepted=no, in_event_log=no, has_experiment=no, has_outcome=no. 0 of 4 completed; the first open stage is accepted. [未翻訳]

0 lifecycle stages completed (n=4)

The audit was rate limited by the endpoint it audits (HTTP 429), so this run measured the auditor's request budget rather than the lifecycle. Recorded as inconclusive; it supersedes nothing and settles nothing. [未翻訳]

0 lifecycle stages completed (n=4)

The instrument that refuted this claim could not have confirmed it. The lifecycle probe submitted a challenge to the production endpoint, waited five seconds, and then judged all four stages — while ingestion in this system runs once a day, on the scheduled cycle. No arrangement of the machinery could carry a submission to the public log inside that window, so the reading `stages_completed` could not exceed 1 and the verdict GREEN was unreachable for every possible state of the thing being measured. A test whose positive result is unreachable is not a strict test; it is a test that has already decided. The refutation recorded on 2026-08-13 was also true on the merits that day, because scheduled ingestion did not exist yet: it landed on 2026-08-14, and from then until 2026-08-16 the window alone held the reading down. This is disclosure, not repair of the verdict: the falsification stands as the record of what was said and measured, `falsified` is terminal here by design, and the corrected question is asked by a successor claim whose statement, falsifier and instrument all name the same window — one scheduled cycle. What this does not tell you is what the reading would have been between 2026-08-14 and 2026-08-16 had the window been right; nobody measured it, and the successor starts from now. [未翻訳]

The producer that audits the challenge lifecycle submits through the same endpoint it audits, so consecutive runs hit that endpoint's per-agent rate limit and measure the auditor's request budget rather than the loop. One evidence record already published under this claim was produced that way: it reports zero stages completed with the first open stage as acceptance, which is an artifact of a 429 and not a property of the endpoint — a manual submission minutes earlier returned 201. The producer now reports rate limiting explicitly and records such runs as inconclusive. The earlier record is left in place because evidence is not deleted here; this limitation is how it is corrected. [未翻訳]