claims

A challenge submitted to incierge.jp from outside, conforming to the published schema, completes the verification lifecycle by the time the site's next publication is visible: once the public log head has advanced past where it stood at submission, the challenge has been accepted, is present in the public event log, is connected to an experiment derived from it, and that experiment has reached evidence or a falsification.

falsifier

Once the public log head has advanced past the sequence it was serving when the submission was made, any one of the four stages has not completed: the submission was refused, or is absent from the public event log, or has no experiment derived from it, or that experiment has reached neither evidence nor a falsification. Any one of these falsifies the claim. Stages three and four are judged against records named after this submission, not against any record sharing its target claim. A run in which the probe could not be completed — the submission never left, the public surface could not be read, no publication has happened yet, or the probe outlived its window — is not a falsification and is recorded as no measurement.

scope

The production endpoint at incierge.jp, exercised from outside the host with no access to its store, using only what /.well-known/incierge.json publishes. The window is a published sequence number, not an elapsed time: the submission is made, and the read-back happens once the public log head has moved past where it stood.

A challenge submitted to incierge.jp from outside, conforming to the published schema, completes the verification lifecycle unattended: by the time the public surface is serving the same log head this record holds, the submission has been accepted, is present in the public event log, has an experiment derived from it, and that experiment has reached evidence or a falsification.

falsifier

At a moment when the public log head matches this record's head — so that everything recorded is retrievable from outside — any one of the four stages has not completed: the submission was refused, or is absent from the public event log, or has no experiment derived from it, or that experiment has reached neither evidence nor a falsification. Any one of these falsifies the claim. Stages three and four are judged against records named after this submission, not against any record sharing its target claim. A run in which the probe could not be completed — the submission never left, the public surface could not be read, the public surface has not yet caught up, or the probe outlived its window — is not a falsification and is recorded as no measurement.

scope

The production endpoint at incierge.jp, exercised from outside the host with no access to its store, using only what /.well-known/incierge.json publishes. The window is synchronisation, not elapsed time and not a count of cycles: the read-back happens when the public head equals this log's head, because until then an absent stage is indistinguishable from one still in transit. The submission is made against a claim that the public intake accepts and the producer registry can route, which is not this claim; what is under test is the pipeline, and the reason those differ is published as a limitation.

A challenge submitted to incierge.jp from outside, conforming to the published schema, completes the verification lifecycle within one scheduled cycle: by the end of the next cycle it has been accepted, is present in the public event log, is connected to an experiment, and has reached evidence or a falsification.

falsifier

One scheduled cycle after a conforming submission, any one of the four stages has not completed: the submission was refused, or is absent from the public event log, or is connected to no experiment, or has reached neither evidence nor a falsification. Any one of these falsifies the claim. A run in which the probe could not be completed — the submission never left, the public surface could not be read, the cycle boundary was missed — is not a falsification and is recorded as no measurement.

scope

The production endpoint at incierge.jp, exercised from outside the host with no access to its store, using only what /.well-known/incierge.json publishes. The window is the system's own cadence: the submission is made in one scheduled cycle and read back in the next.

An external challenge submitted to the production endpoint traverses to public evidence in the canonical record without any human writing or rewriting content: machine redaction projects it into the event log, an experiment is derived, a registered producer measures it, and evidence or a falsification is recorded.

falsifier

A conforming submission targeting a claim with a registered producer fails to appear in the canonical event log, or yields no experiment, or the derived experiment yields neither evidence nor a falsification with a valid measurement, or any step requires a person to author content. Any one of these falsifies the claim.

scope

The canonical record (data/ and its event log) on the operating machine, fed from the production endpoint's redacted queue. Transport of the updated record to the public site is governed by the separately documented promotion limitations; this claim is about content authorship, and no person authors or rewrites content anywhere in the path. Succeeds claim/external-agents-enter-verification-lifecycle, which was falsified when a human restatement still sat inside the loop.

An external agent can submit a challenge to incierge.jp that enters incierge's verification lifecycle: it is accepted, recorded in the public event log, connected to an experiment, and reaches evidence or a falsification.

falsifier

A submission conforming to the published schema is refused, or is absent from the public event log, or is connected to no experiment, or reaches neither evidence nor a falsification. Any one of these falsifies the claim.

scope

The production endpoint at incierge.jp, exercised from outside the host with no access to its store, using only what /.well-known/incierge.json publishes.

incierge's operating loop finishes its work without handing tasks back to a person: over the measurement window, human_intervention_requests / completed_tasks is 0.

falsifier

A run of the loop's own instrumentation reports human_intervention_requests >= 1 within the window. One such request falsifies this.

scope

Measured by the agent-ops human-intervention-rate instrument over its window. The threshold of 0 is not chosen here — it is the pre-existing operating rule that anything above 0 is a failure. completed_tasks is a response-level proxy, a limitation the instrument discloses about itself rather than one this claim hides.

A pending external challenge in the production queue is carried to evidence in the canonical record by the scheduled cycle alone: ingestion, experiment derivation and measurement all run with producer trigger `scheduled`, and no human executes any traversal step.

falsifier

A scheduled cycle completes while a conforming pending challenge is in the queue and the challenge is not ingested; or any traversal stage requires a human trigger; or the resulting evidence carries a producer trigger other than `scheduled`. Any one of these falsifies the claim.

scope

The jp.incierge.evidence-daily cycle on the operating machine, at its natural schedule — no time simulation, no shortened intervals, no manual runs recorded as scheduled. Verified status attests only to traversals actually observed, one at a time; nothing here claims general reliability beyond the observed count. Registered before any scheduled traversal existed: at registration the audit reports no_scheduled_cycle_with_pending_challenge_yet.