measure(H_1040): 🟢 BASELINE-REGIME-SPECIFIC — pre-rollout-latent uniquely makes big-Φ↓ (H_1033 residual pinned)#1958
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…uely makes bigΦ↓ Held canonical planning intervention FIXED (depth=8, VERBATIM H_973/H_1004); swept 4 baseline regimes. PASS: pre-rollout-latent ALONE makes big-Φ DOWN (d=-1.834) + faithful UP (+2.333); indep-bits / shuffled-time / matched-marginal all RAISE big-Φ. big-Φ ctr -4.0083 reproduces the original H_973 -4.008 exactly → the bigΦ-DOWN sign is dominated by the BASELINE CONTRAST (the high-Φ prior state), pinning the H_1033 residual. Mirror≡stdlib re-proven n=4,5 before scoring. $0 CPU-local, 0 pods/GPU, SERIAL. Verdict .txt = g73 raw. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
H_1040 — which baseline regime predicts the big-Φ-DOWN half? (H_1033 residual)
Measures the pre-registered H_1040 (pre-reg merged #1939). 🟢 BASELINE-REGIME-SPECIFIC (H1 PASS).
H_1033 (⚪ degenerate) found the planning split's big-Φ-DOWN half does not reproduce on any
independent-bits baseline (0/5), deferring: the sign is dominated by the BASELINE CONTRAST, not
task structure. H_1040 holds the canonical planning intervention FIXED (planning_trajectories
depth=8 → H_plan, VERBATIM H_973/H_1004) and sweeps 4 baseline regimes.
Per-baseline-regime contrast (planning − baseline, 30 seeds, Cohen d)
★ = a-priori pre-registered pick. PASS: the pre-rollout-latent baseline ALONE makes big-Φ go
DOWN (d=−1.834 ≤ −0.8) AND faithful go UP (+2.333), while ALL 3 other baselines do NOT make big-Φ
go DOWN → the big-Φ-DOWN half is a planning-vs-(pre-rollout-latent) property, NOT regime-independent.
Key finding
Only the model's OWN prior state (the original H_973 GREEDY, big-Φ=9.53) makes planning LOWER big-Φ.
The big-Φ contrast −4.0083 reproduces the original H_973 number −4.008 exactly → the H_1033
residual is pinned: the big-Φ-DOWN sign is dominated by the BASELINE CONTRAST (the high-Φ prior
state), not by generic task decomposability. faithful is NULL only for time-shuffle (which leaves
the MI matrix unchanged → contrast exactly 0).
Verification (g73 / a_phi_iit4_tool)
(|Δ|≤7.97e-10) BEFORE scoring. Phi from stdlib faithful_phi + iit4_bigphi mirrors only — NO proxy.
Verdict raw:
.verdicts/1040_split_baseline_regime/H_1040.txt. Probe:UNIVERSE/h1040_split_baseline_regime.py.🤖 Generated with Claude Code