CMS EDE artifacts and package outputs for MarketLink.
This page is the operator view of collected evidence, run ledgers, storage boundaries, package formats, screenshots, API JSON, redaction manifests, checksums, and auditor reports.
87 artifacts, 38 source-row references, 14 review/blocker queue items, and 2 blocked package gates.
Raw capture becomes reviewed evidence, then an auditor package
The vault view keeps proof understandable: where it was captured, what CMS source it supports, whether it has been reviewed, and why it can or cannot leave ControlFrame.
Private runner folders retain screenshots, JSON, traces, logs, and source sidecars.
Artifacts are reconciled to toolkit rows, item numbers, source files, and scenario IDs.
PII, PHI, tokens, screenshots, JSON, and text extracts need reviewer disposition before export.
The package gate assembles only approved evidence and disclosed blockers.
Latest evidence artifacts
A CMS auditor should be able to see real artifact shape immediately: step, CMS item numbers, artifact type, checksum, and review state.
Evidence vault repositories
ControlFrame separates raw collector output, reviewed evidence, auditor packages, and chain-of-custody metadata. CMS EDE still reads local collector folders in parts of this workflow; the production vault and object metadata spine are ready for the vault-native migration.
Screenshots, Playwright traces, request/response JSON, logs, and source extracts captured before reviewer approval.
Artifacts approved for auditor use after redaction, checksum validation, source mapping, and reviewer disposition.
The final CMS-facing export bundle assembled only from approved evidence and open-blocker disclosures.
Postgres metadata for runs, evidence objects, export objects, jobs, access logs, hashes, and reviewer gates.