Skip to content

Audit Chain

DevEx › Audit Chain (?tab=audit) is the console’s audit log: who did what, and whether the record is intact. Since 2026-10-31 it also holds the records of what shipped and what was found, as ONE scrolling page of five cards, joined by a spine in the order of the questions: Chain integrity (default, open), Deploy lineage (?tab=deployLineage), Evidence (?tab=evidence), Reviews (?tab=reviews) and Session admins (?tab=sessionAdmins, who may read the chain, last). Each card has its own header, source badge and state, the page has one refresh, and a ?tab= link opens and scrolls to its card; a card reads only once it is opened. (The audit verdicts are a different thing: the Platform, Model & agent and Data audits on the Overview.)

Audit chain

  • GET /api/audit returns a newest-first page and the chain’s verdict. Filters: actor, action, outcome (success, denied or failure), since (RFC 3339 or a duration such as 24h), limit, before (a chain sequence number).
  • GET /api/audit/{seq} returns one record in full with its neighbours’ hashes.
  • GET /api/audit/verify walks the persisted chain and names the first record that was edited, removed, inserted or reordered.

The chain is persisted in the console’s encrypted root and continues across restarts.

Only session admins may read the trail, and the check fails closed: it holds sign-ins, refused sign-ins, revocations, and who armed which agent.

Deploy lineage

“Did my commit ship?” Enter a commit SHA (?sha=, GET /api/lineage). Per image, the stage strip shows merged → agents → built → registry → rolled → running. A commit absent from the store is unmeasured, never “did not ship”. It reads the same record as Clusters › GitOps and links to it.

Evidence

TIDE testing a deployment and showing the evidence: a harness run as a Job, its validated document, and its publication. It is the only card here that writes besides Session admins.

Reviews

What the review agents found, per review type, with a drill-down to each run. See Reviews.

Session admins

GET/PUT /api/session-admins: who may read the audit trail and end another person’s sessions.

  • CONSOLE_SESSION_ADMINS in the console’s Secret only seeds the list on first boot. After that, the list is edited here.
  • Unset means nobody, unlike the other admin lists.
  • A save refuses an empty list, and one that drops you unless someone else remains. Every attempt is audited before the list is written.