docs: restate compression claims to held-out truth; retire ≥3× Abrash gate#95
Merged
Conversation
… gate The ≥3× Abrash compression gate held only on in-sample dev corpora that co-evolved with the primitives. Out-of-sample it does not survive: 1.67× on the blind held-out set, ~1.7× on the 1,145-shape generated distribution, ~1.03× vs fair terse Python. Compression is retained as a niche property (2–4× loop/fold shapes, ≤1× scans/builtins), not the headline. Restated shipping thesis (all measured out-of-sample): agent writability (100% pass@5), per-solution economics (CSPM 2.124× held-out, widening), verified core (5 proof roots) + capability confinement, 487-token preamble. - README.md: measured-results table gains a held-out column and leads with it; Abrash-rule section states the original gate, that it FAILED out-of-sample and why, and the restated thesis. In-sample numbers kept, labeled in-sample. - docs/mtl-spec.md: §1.1 gate verdict note, §10.6 parallel verdict, roadmap MEASURE row marked CONCLUDED, new §16 changelog entry, in-sample qualifiers on §5 admission rationale. - bench/README.md: retirement banner leading with held-out 1.67×; headline verdicts relabeled in-sample. - docs/RELEASE-NOTES-0.4.0.md: superseded editor's note atop the frozen v0.4.0 body (recorded numbers preserved).
madmax983
marked this pull request as ready for review
July 16, 2026 01:55
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.
Before / After
Before: the repo headlined a ≥3× compression gate (the "Abrash rule") as MET. The measured-results table led with in-sample figures (T_v0 3.72×, tier-2 3.87×/3.92×) and stated the gate was cleared, presenting compression as the shipping thesis.
After: we lead with the blind held-out (sealed) number, 1.67×, and state plainly that the ≥3× gate FAILED out-of-sample — the 3.7–3.9× figures held only on dev corpora that co-evolved with the primitives (an in-sample benchmark-fitting artifact). Corroborated by ~1.7× on the 1,145-shape generated distribution and ~1.03× vs fair terse Python. The thesis is restated around what actually generalizes, all measured out-of-sample:
Compression is retained as a niche property (2–4× on loop/fold shapes, ≤1× on scans/builtins), not the headline. In-sample numbers are preserved throughout, explicitly relabeled in-sample.
How (files touched)
This is a docs-only claims restatement — no code, primitive, glyph,
spec_step, orOutcomechange, and no spec-version bump.Testing
cargo test --workspace— green, 0 failures (docs-only change touches no code; the largest suites are 97 and 24 passed, every resultok).Generated by Claude Code