Evidence Room
Manage Evidence Factory Jobs, Sealed Evidence Bundles, manifests, verification, downloads, and secure shares.
Evidence Room is the contextual evidence workspace at /evidence-room. Route access requires evidence:list unless a full-access role applies. Its primary-navigation promotion remains demand-gated.
One Evidence Factory
Lineage Explorer supplies investigated records. Audit Trail supplies chronology and source entries. Control Mapping supplies framework and control scope. Policy Builder supplies one exact policy version. Evidence Room can start an unscoped or prefilled request. Every entry point creates the same versioned request and job, except Evidence Room's run-identifier and run-set modes. Those two post to the older POST /v1/evidence/export-jobs endpoint and build no EvidenceFactoryRequest. Evidence Room's time-range mode uses the contract.
flowchart LR L["Lineage Explorer"] --> F["Evidence Factory Job"] A["Audit Trail"] --> F C["Control Mapping"] --> F P["Policy Builder"] --> F E["Evidence Room"] --> F F --> M["Manifest"] F --> B["Sealed Evidence Bundle"] B --> V["Independent verification"]
What it owns
- Queued, running, finalizing, completed, completed-with-omissions, failed, and canceled jobs.
- Progress, structured failure details, an omission count, retention expiry, and lifecycle events.
- Bundle download, manifest loading into the verifier, verification summary, and secure share links with expiry, download caps, and IP allowlists.
- Context selectors for Decision Requests, executions, Lineage Records, policies, controls, Audit Trail source entries, and chronology.
Tenant and actor values come from authenticated server context. The contract validates chronology, a selector limit of 100 per selector, and cross-record consistency. The API and the evidence exporter enforce tenant boundaries against the caller's session before job creation. Completed bundles use the shared manifest and offline verifier contract.
Per-job retry has no control in this workspace. Individual omissions appear in the manifest text loaded into the verifier.
Compatibility export paths have a published sunset window. Customer product actions use the Evidence Factory contract.
