Case lifecycle
A CyberBench case is a chain of acts. Evidence is collected into a hash-linked custody ledger, read and transformed under a validated method, promoted to findings, approved maker–checker, sealed into a versioned case catalog, and only then published. Nothing happens to a case off the record:custody-chain/v1#action-coverage closes the custody vocabulary at six verbs, and each other pack names the act that produces its own document.
Pick a case below, or drop your own documents in. The built-in cases are annotated with the live verdicts of the cyberbench.verify policy suite.
One evidence image, one derived transcript, three seals — ingest, interim, finalisation — a finding approved the next morning and a second finding rejected in review, and a publication gated on the finalisation seal. The policy suite finds nothing to say: this is what a clean case reads like.
A ring rather than a dot is an act an object has not received — a finding version with no approval naming it, a publication with no release decision. That is a state rather than a fault:finding-approval/v1#supersession-and-publication-invariant owes a finding an approval only where a publication composes it.
Open the workbench ↗ — the same case full-bleed, without the documentation chrome.
The flow view · the lane chart ·the standards graph shows the same pipeline as types ·standards registry.