provenance_
a flight recorder for agent fleets. every decision, every option it rejected, every human verdict: one tamper-evident file.
chain verified
agent starts drafting a launch post → ✗ process killed mid-decision → ↻ resumed from the ledger alone → completed output byte-identical to an uninterrupted run

The trail

A real ledger from a real run, not a mockup. The red row is the scar where the process died: a decision opened and never committed. Resume replayed the fold, pinned the committed past, and re-entered exactly that decision. Click any row.

You hold the pen

The whole thesis in one interaction: your verdict becomes a training pair, and the pair moves a policy. Overrule the headline decision and watch it propagate. Nothing is written; this plays out on an in-memory copy.

Exports: the same trail as training data

Verdicts turn the log into labels. Edits become preference pairs. Rubber-stamp approvals get filtered, and the receipts say so.

The alignment score

Held-out decisions, replayed. Same mechanism both times; the only difference is whether the policy saw the organization's own ledger. Counts, not vibes.

The artifact it was writing

The launch post the agent produced (before verdicts were applied). Killed halfway through, resumed, byte-identical.