06 — DOT stamping + registry/ledger consistency (row 24; A14; §5.7)

Per-phase DOT/staging stamping

• P1 (p1b-meta.sql): creates sbx_meta schema + birth_certificate, admission, sandbox_registry, object_registry, dot_manage_ledger; inserts birth (typed expires_at), admission (staging-auto / DOT-100-staging-lite / ADMITTED), registry row (status='active'), ledger op sandbox_create.
• P3 (p3:59-65): object_registry rows for all 6 created objects + ledger op c1_vocab_build.
• P4 (p4:18,23): registers c1_verify + ledger op c1_verify (verified count).
• P5 (p5:38-39,51): registers c1_test_results,c1_run + ledger op c1_bad_input_harness.
• P6 (p6:38,49-54,84-86): registers c1_digest; gate REQUIRES the P3/P4/P5 ledger ops to exist; on pass stamps ledger op c1_evidence_readback carrying the combined digest.
• P2 (drop): host-side staging ledger sandbox_drop_attempt (before drop) then sandbox_drop_success (only after readback proves the DB is gone), plus a tombstone of the birth_certificate to _tombstones.jsonl (the in-DB registry dies with the DB).

No staging artifact lacks a stamp; no official artifact carries a staging stamp (the staging ledger is a host file under /opt/incomex/staging/c1/ledger/ and the in-sandbox ledger lives in the sandbox DB — neither writes the official dot ledger / dot_tools). A14 refuted.

Registry sha256 cross-check (row 24) — POST-FIX

registry/primitives.jsonl = 6 rows. Every row's sha256 (bin), sql_sha256, and common_sh_sha256 were recomputed against the deployed files: ALL_REGISTRY_SHA256_MATCH (6/6). All rows flagged official_runtime=false, deployed_to_dot_bin=false, registered_in_dot_tools=false, status=admitted. Because the R3-SELF-1 fix touched only plan/README/ROLLBACK/ledger (not any registered primitive), the registry cross-check still passes unchanged — proving no registered primitive was altered.

Ledger (ledger/dot_manage.jsonl) — POST-FIX

10 entries, all valid JSON:

seq 1 staging_lane_init · 2 primitive_admission · 3 primitive_deploy · 4 primitive_register
5 reuse_first_reconfirm · 6 primitive_patch_r1 · 7 static_no_write_revalidation
8 primitive_patch_r2 · 9 static_no_write_revalidation_r2 · 10 plan_patch_r3_self_gate (NEW)

seq 10 records the R3-SELF-1 finding, the fix, the 3 changed-file sha256, the re-validation results, and official_before_equals_after + staging_dbs=0 + dry_run_executed=false.

Stamp/ledger conclusion (§5.7)

DOT stamping is present and complete across P1–P6 + P2; registry and ledger entries match the deployed primitives; sha256 consistency holds. No HOLD on C1_STAGING_SELF_GATE_HOLD_DOT_STAMPING_INCOMPLETE.