board: correction — mint_factored is split-brain across ruff branches, not on main

The 2026-07-02 OGAR+ruff review fan-out falsified a claim in the #625
record: ruff main carries mint + soc.rs; mint_factored + RadixCodebook
live only on claude/medcare-ruff-csharp-sync-4iahey (505fdc4), which
diverged before the soc promotion and lacks soc.rs — no branch carries
both. E-BRICK3-CORRECTION prepended; dated correction line appended to
the #625 PR_ARC entry per the corrections-append rule.

Author: claude

.claude/board/EPIPHANIES.md

@@ -1,3 +1,31 @@
+## 2026-07-02 — E-BRICK3-CORRECTION-MINT-FACTORED-IS-SPLIT-BRAIN — the "corrected minter" exists only as the UNION of two diverged ruff branches; no branch carries both mint_factored AND soc.rs
+
+**Status:** CORRECTION (of `E-BRICK3-RAN-TRUNCATION-DISALLOWED` + PR #625's
+`ast-as-partof-isa-address.md` "brick that ran" section, both of which state
+`mint_factored` shipped).
+
+**The finding (review agent, ruff @ b459ec3, verified via git show/diffstat):**
+ruff main carries `ruff_spo_address::{mint, soc}` — the naive minter (with its
+own falsification recorded in its doc header) plus the 256-cap-is-a-lint
+classifier. **`mint_factored` + `RadixCodebook` + `ONTOLOGICAL-RADIX-TRIE.md`
+live ONLY on branch `claude/medcare-ruff-csharp-sync-4iahey` (tip `505fdc4`)**,
+which diverged BEFORE the soc promotion and therefore LACKS `soc.rs` (branch↔main
+diffstat: `soc.rs | 335 ---`). A naive merge of that branch would delete the
+lint. So: main ships the falsified minter; the corrected minter has never
+coexisted with the lint that motivated it.
+
+**Consequence:** the single highest-leverage small move in the address stack is
+rebasing `mint_factored`+`RadixCodebook` over main (conflict surface ≈ the
+`pub mod` line + doc header) so the corrected state exists on ONE branch.
+Until then, "brick-3's corrected form is shipped" is true only of the private
+probe run, not of public ruff main.
+
+**Process note:** my #625 record propagated the claim from the private archive's
+RESTORE-STATUS without re-verifying WHICH branch carried the code — the same
+verify-by-reading-not-by-inheriting failure mode as the stale-doc-comment
+episode (E-BRICK3 arc). Corrections cite their pass: surfaced by the 2026-07-02
+OGAR+ruff review fan-out.
+
 ## 2026-07-02 — E-V3-PLANNER-TWO-NATURES-AND-SPEED-PROBE (operator: planner too slow for sub-µs; resonance-based thinking is not DataFusion)
 **Status:** FINDING (operator-ruled; speed claim probe-gated per truth-architect discipline)
 

.claude/board/PR_ARC_INVENTORY.md

@@ -68,6 +68,8 @@
 
 **Cross-ref:** #616/#617 (the ast-address doc lineage); #623 (OGAR sink-in plan); OGAR #145/#146 (OSINT mint + zero-rows ruling); ruff `b459ec3` (`ruff_spo_address` + `soc`); `E-CODEBOOK-MINT-IS-A-CROSS-REPO-ARC`; MedCare-rs private archive (RESTORE-STATUS re-fetch log).
 
+**Correction (2026-07-02, from the OGAR+ruff review fan-out):** the Locked line's "`mint_factored` … is the corrected minter" overstates its location — on public ruff main only `mint` + `soc.rs` exist; `mint_factored`+`RadixCodebook` are stranded on branch `claude/medcare-ruff-csharp-sync-4iahey` (`505fdc4`), which predates and LACKS `soc.rs`. The corrected-minter state exists only as the union of two diverged branches. See `E-BRICK3-CORRECTION-MINT-FACTORED-IS-SPLIT-BRAIN`.
+
 ---
 
 ## #627 lance-graph: classid canon:custom flip TRIGGERED — migration plan v1 + operator ruling record (doc-only)