KB-2177

RS3C — Index: Source Recovery and RS3B Affected Rerun — 2026-06-21

4 min read Revision 1
rs3cindexsource-recoveryrerun2026-06-21

RS3C — Index: Source Recovery and RS3B Affected Rerun — 2026-06-21

Macro: RS3C — SOURCE RECOVERY + RS3B AFFECTED RERUN WITH CODE-LEVEL BEHAVIOR RECONSTRUCTION Date: 2026-06-21 · read-only · 0 mutations · no allowlist patch · no service restart Package verdict: RS3C_READY_FOR_CODEX_REVIEW · controlling source finding SOURCE_CONFIRMS_UNSAFE_REGISTRAR_BEHAVIOR · REGISTRATION_HOLD · CAN_PROCEED = NO Triggered by: Codex ACCEPT_RS3B_HOLD_AND_PROCEED_TO_SOURCE_RECOVERY (C1/C2/C3).


1. One-line outcome

Both source files (dot-dot-register, dot-catalog-sync) were recovered and hash-verified byte-identical to the deployed OPERATIONAL VPS files via a read-only local code channel cross-checked against wf_fs_dot_bin_snapshotno allowlist patch or service restart needed. Source confirms the operational registrar is unsafe for governed registration; Codex C1/C2/C3 are resolved/confirmed/reconciled; registration stays HOLD.

2. File inventory

File Title Sub-status
01-source-access-recovery-proof-2026-06-21.md Source access recovery proof SOURCE_ACCESS_RECOVERED (Method 3 + snapshot hash)
02-source-mirror-and-hash-record-2026-06-21.md Faithful line-level mirror + sha256 SOURCE_MIRROR_HASH_MATCH (both files)
03-registrar-code-behavior-reconstruction-2026-06-21.md Registrar reconstruction (B1–B23, line-cited) SOURCE_CONFIRMS_UNSAFE_REGISTRAR_BEHAVIOR
04-catalog-sync-code-behavior-reconstruction-2026-06-21.md Catalog-sync reconstruction (C1–C16) writes only meta_catalog.record_count
05-rerun-dual-writer-boundary-source-aware-2026-06-21.md Dual-writer boundary DUAL_WRITER_ON_REGISTRY = DISPROVEN_BY_SOURCE
06-rerun-single-artifact-contract-source-aware-2026-06-21.md Single-artifact contract SINGLE_ARTIFACT_CONTRACT_CONFLICTS_WITH_SOURCE
07-rerun-replay-nonce-logical-attempt-state-machine-2026-06-21.md Replay/nonce/logical/attempt (C1) REPLAY_C1_RESOLVED_AT_DESIGN · REPLAY_DOMAIN_FAIL_CLOSED
08-rerun-pair-guard-cardinality-correction-2026-06-21.md Pair/guard cardinality (C2) PAIR_CARDINALITY_CORRECTED_BY_SOURCE
09-rerun-trigger-inventory-reconciliation-2026-06-21.md Trigger inventory (C3) TRIGGER_INVENTORY_RECONCILED (13 user + 4 FK)
10-updated-adversarial-matrix-and-fail-open-cases-2026-06-21.md Adversarial matrix 50 cases (40 + 10 new)
11-rs3c-decision-packet-2026-06-21.md Decision packet RS3C_READY_FOR_CODEX_REVIEW
codex-review-packet-rs3c-source-recovery-rerun-2026-06-21.md Codex review router requested verdict
rs3c-index-…-2026-06-21.md this index
../macro-rs3c-source-recovery-and-rs3b-affected-rerun-2026-06-21.md executive rollup

3. Codex correction status

  • C1 (nonce durable consume): RESOLVED (design) — RS3C-07.
  • C2 (cardinality): CONFIRMED BY SOURCE — RS3C-08 (one row, paired_dot field).
  • C3 (trigger count): RECONCILED — RS3C-09 (13 user = 12 enabled + 1 disabled; "14" over-counted).

4. Hash record (fidelity oracle)

File sha256 Deployed match
dot-dot-register (operational) 31d5cf1508c7950cc30a2a6abb46d7cee868e1cbf951a6095ff0aee7ba48583f OPERATIONAL (id 6022) ✅
dot-catalog-sync (operational) 7dd84cda6d1e220fc7f54419bf40ec9ad05a952b6a402360df73f0af3fa355cd OPERATIONAL (id 5963) ✅

5. Next step

Registrar-hardening DESIGN macro consuming the recovered source + four envelopes, gated on the G2 Owner-of-record decision. No implementation, no registration, no live registrar patch. Builds on RS3B; consumes Codex C1/C2/C3.