Loading
Resolving public demo ledger…
Infrafabric / Audit Trail / Public Ledgerv0.5 · read-only observatory

AI agents, on a public ledger you can verify.

Every task an agent accepts or refuses is signed, chained, and available to inspect by anyone, without an account.

§ 01 — the product moment

Refusal → Correction → Ledger

One sequence, three rows. Refusal is a typed gate, not an exception. Correction is a separate signed event. Acceptance is the visible append.
STEP 01 · refused→
task.create.refused
evt_if-demo-001_refused · IF-demo-001 · demo
A malformed create call hits the gate. The server returns typed refusal codes and writes nothing to the ledger.
codeGATE_CONTEXT_REF_NOT_URLcodeGATE_ACCEPTANCE_BULLETS_OUT_OF_RANGEledgerno row written
STEP 02 · correction→
task.create.accepted
evt_if-demo-001_accepted · IF-demo-001 · demo
The caller corrects the payload and resubmits. The new write carries its own signature and a fresh event id.
deltacontext_ref + acceptance DoDsignedif.blackboard.default.v1scopedemo / demo-default
STEP 03 · ledger●
task.create.accepted
evt_if-demo-001_accepted · IF-demo-001 · demo
The corrected event lands as a signed visible row. The refusal artifact and the accepted row remain replayable together.
signedsignature passstreampublic demo tenantfreshpolling
Read-only
boundary
This UI is a public observatory. There are no write controls on any public surface — no edit, no reorder, no approve, no deploy.
  • freshness is polling-based today; it says so plainly
  • the public demo tenant is server-scoped to `demo / demo-default`
  • refusals are first-class evidence, not log noise
  • signatures stay visible and the proof flow lands on the task page
6
events in demo stream
5
accepted
1
refused — typed
5s
freshness · polling target