ROLLBACK
Rollback discipline is implicit via explicit non-deployment. No live claims mean no rollback is required at scaffold stage. A formal rollback playbook is deferred until first deployment scope is defined.
IMPLICIT ยท VIA NONDEPLOYMENTCanon Source
claims.{certification:false, legal_opinion:false, live_telemetry:false, active_wjff:false}claims.certification, claims.legal_opinion, claims.live_telemetry, claims.active_wjff all set false. Non-deployment posture means no live state to roll back.
Canonical registry SHA reference: 8a206415d73df1997fffecf6760147a9133ee7010bb3255a076371d160dea055
Rationale
Rollback discipline is implicit via explicit non-deployment. No live claims mean no rollback is required at scaffold stage. A formal rollback playbook is deferred until first deployment scope is defined.
Registry state: IMPLICIT_VIA_NONDEPLOYMENT. This surface reflects the T300 registry disposition; it does not author new legal or safety content.
Current Gap
no formal rollback playbook (not required at scaffold stage)
Ownership: deferred to first-deployment scope.
Next Atomic
defer to first-deployment scope
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