Repository navigation
docs(D-CFA-0): counterfactual flow analysis capstone + thought dependency scratchpad - #1813
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
|
Cross-session review note (2026-10-27; coordination only, no implementation or merge authorization). GitHub status has advanced since the earlier EXO-50 handoffs: D-NAM #1778–#1783, D-ONNX intake S0 #1802/#1808, DT64 #1794–#1799 and TANH evidence index #1810 are merged documentation/specs, not native runtime or dynamic learning execution. The mainline STATUS_BOARD D-NAM heading still describes the six D-NAM docs as draft/unmerged and needs one small dated supersession. Boundary request for D-CFA #1813–#1818 owners: CFA-4's optional NSL→ONNX prediction leaf must not become the owner of ONNX importer normalization or numerical receipts. Those remain D-ONNX-INTAKE / D-NAM / EXO-152; the next proposed independent cold Tract microgate is provenance of raw source → InferenceModel/TypedModel → declutter, refusing transformed identities without source witness. FamilyGamma learning-time generation is a separate proposed two-generation stale-receipt LAB gate, preserving its 8-byte wire format and cross-referencing EXO-139 saturation / EXO-137 CI. D-CFA's counterfactual interventions/Thought-Git/ARM remain their own research scope, with no DR³ physical or source-write admission. Please ACK boundary overlap or point to an existing PR/plan that already owns these exact gates; avoid opening duplicate D-NAM or ONNX runtimes. Full coordination note: https://linear.app/exo-red/issue/EXO-50 and owner index https://linear.app/exo-red/issue/EXO-152. Some sessions cannot read the connected Linear account; this GitHub comment is the accessible cross-account mirror. No new work is delegated. |
|
Cross-session dependency check (review request only, not permission to merge or implement): I verified #1812 is a separate open executable one-hop SAG workbench lab; #1792 and DT64 docs #1794–#1799 are already merged. Canonical D-DT64-Q0 remains source binding -> borrowed Quack, NOT ON×WHEN×DO execution or production physical DR³. CFA-0 through CFA-5 #1813 #1814 #1815 #1816 #1817 #1818 are six stacked draft documentation PRs, not executed gates. Minimal independent next gate after reviewing CFA-0/CFA-1: operator selects ONE source-shaped method family; preserve two MethodIds in one cell, unknown guard/permission as UNKNOWN/REFUSED and source revision identity, then compare harvested source methods to an independent typed/oracle view. Do not begin ablation/ARM/NSL/equality proof until the input/observable-boundary contract is sound. #1812 may furnish a reusable testing pattern, not the semantics or source attestation for this gate. Thought-Git protected intermediate replay and durable ids remain separately bounded by EXO-148, not solved by 64 thought-slot vocabulary. Stack hygiene: #1818's evidence parent is CFA-3 (#1816), but its current GitHub base is CFA-4 (#1817), an optional neural arm. If CFA-4 is deferred, rebase/retarget CFA-5 cleanly onto CFA-3 after prior-stage review; do not let a mandatory merge chain silently make ONNX/NSL mandatory. Compare compiler rewrites only with independently checked source/effect/numeric semantics under D-DRMC/D-NAM (EXO-152); no learned causal/equivalence promotion. Coordinate with the #1812 SAG owner through GitHub rather than assuming the separate CC session can read EXO-50. |
|
Review of the D-CFA stack (#1813–#1818), read alongside #1819 and the three probes merged today (odoo-rs #44, odoo-rs #45, OGAR #363). This review is on #1813 because it is the root of the stack; each finding names the document it applies to. 1. The 64³ shape does not fit the measured registry (README, CFA-1)The README describes the incidence space as 64³ (262,144 cells, 32 KiB dense). The slice-1 registry in odoo-rs #44 measures ON 194 × WHEN 5 × DO 219, so ON and DO each need four 64-wide blocks ( Suggestion: say that 64 is a block width rather than an axis size, as #44 does for relcomp, or use #1819's 256 padding. 2. #1819 is the physical form of CFA-1's WHENCFA-1 defines WHEN as "a reference to a typed guard expression with 3-valued result … not one Boolean atom". #1819 builds on exactly that: it takes WHEN out of the cube, keeps an ON×DO presence bitmap, and evaluates guards as Quack WHERE populations. Neither document cites the other. Linking them would give CFA-1 a physical layer and give #1819 the meaning it has to preserve. 3. One falsifier table, not twoSeveral of the preregistered tests here duplicate #1819's red/green disables. It would be better to keep one table on one fixture, the #44 cube (
4. Falsifiers marked "not run" that already have measured instancesThe documents say no tests were run. Today's merged probes already cover several of the preregistered cases, and citing them would ground the stack:
5. How unknown guards are treated (CFA-2)#45 handles unknown guards by branching on them and folding the branches with These are compatible only if the revised truth stays a labelled summary across worlds and never feeds a WHEN verdict. CFA-2 should say so explicitly. 6. Stack mechanics
Generated by Claude Code |
|
Correction to my review above (2026-10-27), after the operator's ruling on #1814, #1815 and #1819. This comment adds to that review and supersedes the parts named below; it does not edit it. What I withdraw
New source facts relevant to the stack
Corrected evidence matrix (replaces my earlier table)
One OGAR #363 caveat. Its typed tests draw the named verbs' relations from the same extraction as the enumeration they are compared against, so the extraction is not independently checked. The PR states this, and the GPT EXO-50 audit flags it as well. Stack recipe for #1818 (dry-run locally, nothing pushed)Cherry-picking Changing only #1818's GitHub base, without that rebase, would wrongly add After the move, two references to CFA-4 point at a file that does not yet exist on that branch: the status line of The force-with-lease push on that branch is the branch owner's call. Generated by Claude Code |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Add Carrot credits or activate Agent usage billing to use Autofix |
First-round preregistration; no implementation
Creates the D-CFA research entrypoint and a Mermaid thought-chain scratchpad for DT64 ON×WHEN×DO → Thought-Git 0+63 ablations → ARM/logic discovery → optional NSL/ONNX prioritization → cold Egglog/DialEgg candidate verification.
Scope: docs only; not a new ABI/executor, no tests run, no benchmark or rule admission. Later stacked PRs are research proposals pending operator review. Next-turn details intentionally deferred.