docs(core): document + pin the ×3 cascading-flux weighting (closes #2546) - #2631
Merged
Merged
Conversation
Behavior-preserving resolution of #2546's ask (half 1). The state_mutation x3 weighting was invisible outside the source and mis-described by the corpus that discovered it: it is a 150-char proximity radius per mutation WITHIN the same function (correlate_scoped), not a blanket per-function branch-context toggle. - spatial_correlation.py: full semantics comment at Block 6 (scope, the recoverable-raw formula via amplified_cascading_flux, the #2535 phantom- trigger caveat). - core/README.md: new "Proximity correlations" table documenting ALL six dampener/amplifier pairs (radii, multipliers, telemetry keys) -- the flux row in detail. - tests/core_engine/test_spatial_correlation.py: 5 micro-repro pins -- x3 within radius same-function; x1 with no branch / beyond 150 chars / cross-function; per-mutation accounting with raw-recovery assertion. No parsing or scoring change: zero golden-master impact. Half 2 (phantom branch context from unshielded string literals) deliberately remains with #2535 -- that is where the corpus's state_mutation medians actually move. Closes #2546 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BsVATdyMPhUoAUNBKbMUVi
squid-protocol
added
core-engine
Contributor
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
1 participant
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.
Summary
Behavior-preserving resolution of #2546's own ask (half 1: "document it"). No measured number
changes anywhere — this makes the deliberate ×3 weighting visible, correctly described, and
pinned so it can't drift silently.
The corpus's original description was subtly wrong and is corrected here: the weighting is a
150-character proximity radius per mutation within the same function
(
correlate_scoped), not a blanket per-function branch-context toggle — corpus probe functionswere just shorter than the radius. Raw counts were always recoverable
(
recorded − 2 × amplified_cascading_flux, surfaced per file in the audit report's"Contextual Mitigations & Amplifications"); now that's written down.
Changes
spatial_correlation.py— full semantics block at Block 6 (The OOM Bomb): scope, therecoverable-raw formula, the prism/detector: string-literal shielding is selective by signal family (if/try/open count inside a literal, eval does not) #2535 phantom-trigger caveat, corpus provenance.
core/README.md— new "Proximity correlations" table documenting all six silentdampener/amplifier pairs (radii, multipliers, telemetry keys — including the ×100
exfiltration amplifier and ×5 race amplifier no doc mentioned), flux row in detail.
tests/core_engine/test_spatial_correlation.py— 5 micro-repro pins: ×3 within radiussame-function; ×1 with no branch / branch beyond 150 chars / branch across a function
boundary; multi-mutation accounting with a raw-recovery assertion.
Full core suite 588 passed; audit_check all clear. Zero golden-master impact.
What this deliberately does NOT do
Half 2 — phantom branch context from branch keywords inside unshielded string literals
tripling real nearby mutations — stays with #2535, per the issue. That's where the rosetta
corpus's
state_mutationmedians (andhigh_risk_execution/io/doc) actually move.After this merges, the corpus ledger entry
state-flux-branch-weightinggets its semanticscorrected and the per-language tracking issues' state_mutation residuals re-point to #2535
alone.
Cross-repo
residuals — the re-pointing lands in the ledger PR).
🤖 Generated with Claude Code
https://claude.ai/code/session_01BsVATdyMPhUoAUNBKbMUVi