Repository navigation
Conversation
The validator, reader and made-up fixtures of sentier-diagnostics-fixes/1 (SPEC 16.12, step 2). errors() checks a file on its own: shape and limits, every fix's counts and verdicts worked out again from its effect and the base, pairs, and every built set the file calls independent against the sum of its effects. against() and beside() hold it to its diagnostics file and matrix; `check` dispatches to it and prints what the file is made of. A listed pair carries the measured size of its cross term (`largest`), as sentier-bafu proposed: an estimated set then says how far it may lie from its sum, and a built pair is held to its stated size. SPEC 16 now says what the code decided: the rule without the chain's total tolerance, closer/further null on a fix, a claim that names its items, a set where the base has no result, the noise of the built-set check, pair terms, measured sizes, and the open questions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…te, pairs without text
Four questions the fixes format left open, settled before any producer writes a file:
- A pair holds no text: {fixes, kind, reach, largest}, its kind one of five places where
two changes of h = c·B·A⁻¹·f meet. A reason in words names the model, and a check of
text catches identifier shapes, not names.
- `requires`: a fix that cannot be applied alone names the fixes it needs, earlier in the
file. Its effect and counts are measured against their build (a fix with what it
requires, or a built set of exactly those fixes); choosing it chooses them; a fix and
one it requires are never a pair.
- A fix may bring items no state holds: after the matrix's items, base null, and some fix
or built set gives each a result.
- A built set may name the state of the chain it is (the release with every fix); the
check holds the two builds to each other by the rule.
A set's result at an item is now the measured one wherever a build inside the set covers
every fix that changes it, and otherwise each effect on top of what it was measured with.
The independence check still sums the fixes alone, so tolerances do not stack.
48 fixes tests (was 30); 43 of 43 sabotage probes caught; check of 100 fixes on 11,947
items x 25 indicators: 2.7 s.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…st build once per indicator counts() of a 50-fix set at 11,947 items x 25 indicators: 2.6 s -> 0.87 s. The base's own classes were worked out six times per call (2 million classify calls); they are now built once and only when a count needs them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… review Noise belongs to a build, as it belongs to a state (SPEC 5.3, Manuel: "sum, go ahead"): - the base's noise is its state's (`of.base_noise`, left out where the base is the published results, which are exact), held to the diagnostics file; a diagnostics file whose states carry no noise is refused; - a fix is judged with the noise of its build and of the build it was measured against; - a set takes the sum, over its fixes, of both (the base once for each fix measured against it), or the noise of a build it takes a result from and the base's, where larger; it says at how many builds the noise is known; - a built set is held to its sum with the noise of every build both sides stand on, and to its state with its own noise and the state's. The matrix of #22 writes a result equal to the one before as "=": the base and the state check read it written out. From sentier-bafu's review as producer (12 fixes and the release, written from its chain): - `largest` is the rule's own measure, the smallest tolerance under which a built pair agrees with its sum (`size_of`); "no size" where none is enough, apart from null (not measured); a pair with no size must be built, and its build must have none; - the kinds of pair are in their order of precedence: same entry first; - an item a fix brings in a unit no item of the chain has takes a floor of 0 from nothing; - SPEC 16: effects on the base's route, results read exactly, reach counted on the build with both fixes, the premise of the list of pairs for fixes that edit data. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mklarmann
force-pushed
the
fixes-format
branch
from
November 17, 2026 05:59
5806c4c to
cbbb7f0
Compare
mklarmann
force-pushed
the
fixes-validator
branch
from
November 17, 2026 05:59
a53589e to
37b2cee
Compare
sentier-bafu's review as producer (finding 1): a set's noise summed over every ticked fix put an item that moved 2.9 % within noise as soon as an unrelated fix was ticked (A30 again). Each item now takes the noise of the builds its result stands on: a build's item that build and the base; a summed item the fixes that change it, each with what it was measured against, summed in the order of the file so the page's port matches bit for bit. The built-set check takes the same per item. compose gives the noise of each item (item_noise) as the reference for the port. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
sentier-bafu's review of 8c7f2c3 (nothing blocking) found three mutations the tests let through: - a sum in id order: the three fixes of the order test were already in id order. Six fixes now, out of id order, with noise whose sum in file order only one other order of the 720 gives (its first two swapped); the test asserts that it still tells the orders apart. - a sum in the set's own (hash) order: caught on some seeds only; now on 30 of 30. - the built-set check without the base at an item none of the set's fixes change: a built set of a and b moving p3 by 1.2 % passes with the base's noise and its own (1.5 %), not with its own alone. SPEC 16.5: a set that changes nothing in an indicator stands on no build there; the page says nothing changed, never "not measured". Co-Authored-By: Claude Opus 5.5 <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.
Summary
Step 2 of SPEC §16.12: the reader, validator and made-up fixtures for
sentier-diagnostics-fixes/1. A fixes file holds one base state and fixes, each measured on its own against that base. Stacked on #23 (SPEC §16), which Manuel approved, and on #22 (noise per state, the matrix's"=").Four questions settled here, before any producer writes a file (§16, for Manuel to agree in this PR):
{fixes, kind, reach, largest},kindone of fivesame entry,technosphere,technosphere and emission,technosphere and factor,emission and factor, in that order of precedencerequires, earlier in the filestateon a built setNoise belongs to a build (§5.3 from #22, Manuel: "sum, go ahead"). A comparison takes the sum of the noise of the builds it stands on, never of one it does not:
A fix that does not change an item adds nothing to it: sentier-bafu's review found that a noise summed over every ticked fix put an item that moved 2.9 % "within noise" as soon as an unrelated fix was ticked (A30 again). Per indicator a set says its largest item noise and at how many of the builds those items stand on the noise is known (
{value, known, builds});composegives each item's noise (item_noise), the reference for the page's port. Not measured is never none.A set's result at an item:
The independence check sums the fixes alone, without a built set inside: otherwise a set within tolerance of a build that is itself within tolerance of the sum would pass at twice the tolerance. A test pins this.
From sentier-bafu's review as producer. It wrote a file from its own chain (BAFU:2026 v1, 11,947 items × 25 indicators): 12 fixes and the release, checked clean in 1.9 s. Taken in:
largestis the rule's own measure (size_of): the smallest tolerance under which the built pair agrees with its sum."no size"where none is enough, kept apart from null ("not measured"). A pair with no size must be built, and its build must have none.reachis counted on the build with both fixes.Sparse counting. A fix is counted from the items it changes plus the classes of the build it was measured against, not item by item.
SparseCountsandRequireshold this to a dense item-by-item count.Evidence
sentier-diagnostics-fixes/1.After: 286 Python tests (67 fixes tests) and 82 node tests pass;
ruff checkis clean on the changed files.errors()takes about 2.4 s;counts()of a 50-fix set 1.1 s, of which about 0.4 s is the noise item by item (most of these items are changed by several fixes, so each sums its own; the sum keeps the file's order for the page's port).What I did not check
of.base_noise(read from its base state), each build's noise,largestbysize_ofor"no size", andreachon the build with both fixes.methodwill state that check.Merge Danger
Door: two-way. A new module and format; nothing existing reads it. The only change to existing behaviour is one new branch in
check.Blast Radius: none for current files. Once a producer writes
sentier-diagnostics-fixes/1, any later change to its keys means a new major version (SPEC 4.1). That is whyrequires,state, added items, the pair shape,base_noiseand"no size"are in now.No reviewer requested. Reviews stay in-house between the sessions for now. Manuel merges.
🤖 Generated with Claude Code