08 — Readback & rollback

KB readback (AgentData)

Package path: knowledge/dev/laws-new/reports/sovereign-bootstrap-dot-apr-approve/

00-index.md
01-sovereign-bootstrap-warrant.md
02-existing-identity-and-approval-channel-reuse-first.md
03-dot-apr-approve-minimal-design.md
04-authenticated-approver-substrate-proof.md
05-dot-apr-approve-lifecycle-proof.md
06-self-approval-guard-and-null-proposer-risk.md
07-fail-closed-tests.md
08-readback-and-rollback.md
09-final-decision.md

All 10 files uploaded to AgentData KB and confirmed present (see 09 §readback). This package is the evidence SSOT for the turn (per dot-manage addendum §2: AgentData KB = report/evidence SSOT).

Rollback

Nothing to roll back. This turn performed 0 production mutations, 0 governed writes, 0 DOT births, 0 catalog/registry/contract/grant rows, 0 approval rows. Before==after on every probed object:

apr_approvals(415)            0 → 0
quorum_passed('APR-0415')     false → false
dot_tools dot-apr-approve     absent → absent
/opt/incomex/dot/bin/dot-apr-approve   absent → absent
qt001_authority_identity_registry      1 row → 1 row (unchanged)
APR-0415 status/payload       pending / md5 43c314bbdecc len 47232 → unchanged

The only writes performed anywhere were to AgentData KB (this 10-file evidence package) — reports/evidence, not governed runtime.

Forward rollback (if the staged plan is ever executed)

Per file 05: each lifecycle mutation has a paired revert (retire DOT, delete the single catalog/dot_tools row, drop the seat/audit tables, additive revert of the bin script). Orphan check after teardown must read 0 dangling contract/registry/grant rows.

Orphan check (this turn)

DOTs created this turn ......... 0
orphan DOTs ................... 0
dangling contracts/grants ..... 0