board(epiphanies): correct over-reach — bundle is math-substrate-valid, JC-owned, not legacy

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MLBnPuScZy6w9di2QEjsXM

Author: claude

.claude/board/EPIPHANIES.md

@@ -14,7 +14,7 @@
 
 **UNBUILT additions (not code yet):** (a) generalize ComputeEdge nodes computed-field → method(THINK/DO); (b) `StepMask` in contract (W3a, queued); (c) const `ClassView` struct-of-methods from codegen.
 
-**OPEN QUESTIONS / where it may be WRONG:** NARS-5 ↔ Pearl-3 is a projection NOT an isomorphism (Revision=write-axis, Synthesis=multi-path — off the see/do/imagine line); the atom set generalizing InferenceType is asserted, unverified. The cost crossover is derivable-in-principle but UNMEASURED (level + sharpness conjectural). The data-cascade/meta-bundle boundary may be fuzzier than a clean line. Whether `dispatch = bitmask-AND over topo-order` reproduces CURRENT routing bit-for-bit is the whole open question — the model could name a style/inference/action the coordinate CANNOT hold, and THAT residual is the valuable result. `I-SUBSTRATE-MARKOV` + `data-flow.md` "BUNDLE" language is VSA-framed = legacy-for-V3 (doc-hygiene, NOT acted on here).
+**OPEN QUESTIONS / where it may be WRONG:** NARS-5 ↔ Pearl-3 is a projection NOT an isomorphism (Revision=write-axis, Synthesis=multi-path — off the see/do/imagine line); the atom set generalizing InferenceType is asserted, unverified. The cost crossover is derivable-in-principle but UNMEASURED (level + sharpness conjectural). The data-cascade/meta-bundle boundary may be fuzzier than a clean line. Whether `dispatch = bitmask-AND over topo-order` reproduces CURRENT routing bit-for-bit is the whole open question — the model could name a style/inference/action the coordinate CANNOT hold, and THAT residual is the valuable result. **Correction (operator, same session): bundle is NOT declared legacy.** Bundle is valid where the substrate is genuinely mathematical (semigroup / Markov / Jirak); WHERE it applies (meta roll-up vs detail cascade vs formal-scaffold pillars) is a MATH question OWNED BY THE JC CRATE (jirak/pearl/ewa_sandwich), deferred — not settled here. The ONLY firm claim is the negative one: VSA-data-**soup at the detail level** is the anti-pattern (register-loss, `I-VSA-IDENTITIES`). `I-SUBSTRATE-MARKOV` / `data-flow.md` BUNDLE framing stays intact pending that JC derivation.
 
 **PROMOTION GATE (reconstruction probe — CONJECTURE→FINDING only when green):** build `think::atom::{…}` as const ClassView method-DAGs; `fanout(StepMask, grid)` Morton-parallel; data reduce = commutative monoid, meta = MetaWord bundle; show (a) reproduces current InferenceType/ThinkingStyle/ActionDef routing bit-for-bit, (b) order-independence across tile-completion permutations, (c) zero VSA in the data path, (d) both commit gates stay distinct. GREEN promotes; RED names the residual (equally valuable). Natural first probes: W3a (StepMask) + #19 (cmpeq_mask ClassView-resolution). Nothing downstream is bound to this until the gate is green.