Decisions and the decision page
The list
Section titled “The list”Decisions shows every record in the workspace, newest first. Above the table a stats strip summarises the workspace: decisions, adverse outcomes, records in the last 24 hours, subjects, sources, signed count and the chain head. The strip refreshes every 15 seconds.
Filters, in the toolbar: free text, subject type and id, agent, source, assurance level, and adverse or not. Filters are in the page address, so a filtered view can be bookmarked or sent to a colleague. Each row shows the decision id, subject, agent and source, the action, the outcome, assurance, custody, the chain position (with a tick when signed) and when it happened. A gavel icon next to an id means a legal hold covers the record.
The decision page
Section titled “The decision page”The header names the record: id, outcome, assurance and custody chips, the subject, the agent, the time and the event count. Verify opens the Verify page with this record loaded; Export evidence downloads the bundle.
Lineage
Section titled “Lineage”The timeline of every event, in order, in the words a reader would use: Input received, Model call · gpt-5, Tool call · orders.read, Policy · refunds_above_100_require_approval v7, Approval · support lead, Action · refunds.issue, Outcome · completed. Approvals and outcomes are drawn filled to stand out. Under each title is one line of detail in monospace: the fingerprints, the rule that fired, the approver, the target. Long timelines are collapsed by default. When originals were uploaded, the lineage says how many of the referenced fingerprints are present in custody.
Affected person
Section titled “Affected person”The subject, whether the outcome was adverse, and the notice workflow: draft, approve, send, withdraw, with a progress rail and the deadline countdown. Below it, reconsiderations recorded for this decision and a button to record one. Notices in detail.
Framework coverage
Section titled “Framework coverage”Per pack, each applicable control and whether this record’s evidence satisfies it, with the gap sentence when it does not. Frameworks.
Integrity
Section titled “Integrity”The verification the API ran when you opened the page: hash, signature, key id, chain position and previous hash, and the checkpoint that covers the record with its timestamp status. This is the server’s opinion; the Verify page is yours.
Participants
Section titled “Participants”Every actor: the agent, systems and humans, with role and identity provider.
Custody
Section titled “Custody”Storage and key custodian, region, retention (the expiry date under the workspace policy, or Kept indefinitely, or Past retention), what the source itself declared about retention, and the legal hold with Place hold or Lift hold for owners and admins. A hold inherited from the subject links to the subject page where it is managed. Retention and holds.
Provenance
Section titled “Provenance”Source, source type, connector version, when it was ingested, the agent version and the record format version.
Records Stratl wrote
Section titled “Records Stratl wrote”Records whose agent is stratl-notices, stratl-retention or stratl-custody are Stratl’s own workflow: approvals, sends, holds, key uses, custody transfers. They are listed with everything else and verify the same way. Filter by agent to see only them.