EVIDENCE
Evidence classes are named on the private-boundary map (case-records, incident-evidence, audit-bundles). Audit-bundle format is not yet defined; evidence chain specification is the next machine-actionable step.
SCAFFOLD ยท LIVE ANCHOREDCanon Source
boundaries.private[case-records, incident-evidence, audit-bundles]boundaries.private carries case-records + incident-evidence + audit-bundles as scaffold classes. Audit-bundle format specification is the outstanding machine-actionable item.
Canonical registry SHA reference: 8a206415d73df1997fffecf6760147a9133ee7010bb3255a076371d160dea055
Rationale
Evidence classes are named on the private-boundary map (case-records, incident-evidence, audit-bundles). Audit-bundle format is not yet defined; evidence chain specification is the next machine-actionable step.
Registry state: SCAFFOLD_LIVE_ANCHORED. This surface reflects the T300 registry disposition; it does not author new legal or safety content.
Current Gap
audit-bundle format not defined
Ownership: machine-actionable specification work.
Next Atomic
evidence chain spec
Provenance Chain
AGENT.md L1725 · CDASA / MEMBRANE / CRF Section 20 verbatim spec reads (item 17 discovery scope)AGENT.md L6558 · Item 18 CRF truthful dispositions (primary critical path)data/crf/CRF_V1_SOURCE_REGISTRY.json · canonical registry cross-referencedata/crf/CRF_V1_RECONCILIATION.json · emission state NOT_DEPLOYED + 26-file historical output SHA256SUMS referencedeploy/cloudflare_pages/crf/index.html · live public scaffold surface