Repository navigation
Conversation
mklarmann
added a commit
that referenced
this pull request
Nov 17, 2026
The page no longer adds up the differences of steps apart. A step's difference was measured with every step before it applied, and an LCA result is not linear in the technosphere, so a sum would use differences measured in a state the set never had. Any set of fixes belongs to a file of fixes measured on one base (SPEC section 16, proposed in #23). On a chain the page compares one step, a run of consecutive steps, or the whole way. A run is judged from the state before its first step and the state after its last, with the largest tolerance and the largest measured noise of its steps. Steps apart, from an address, are refused and the reason is said. The strip and the list choose one step, or with Shift (or Cmd or Ctrl) a run; a group heading chooses its run. The ticks and "the steps where something moved" are gone, since both made steps apart. The page's port of rule.judge is now held to 813 pairs on every edge of the rule, written by tests/test_boundaries.py: the tolerance, the noise, the floor, a sign crossing, ten times, every band edge, factors too large for a float and subnormal results, mirrored and below zero. Probes that turn one comparison of the port from <= to < are caught. together.py judges a run (first, last), and tests/fixtures/together.json holds every run of the local example. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ct or estimated Manuel chose one base with fixes measured on their own over a chain of hundreds of states, a file of fixes of its own, and estimated sets shown but marked (18 November 2026). This section says what that file holds, when a sum of effects is the result, how a set is judged and labelled, how interactions are declared and held to built sets, what the page does and what the validator will refuse. No code yet: the validator follows once the text is agreed. 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
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
A proposal, as text only: SPEC section 16, fixes against one base. A chain is to hold hundreds of fixes, and a reader can choose any set of them. Manuel decided the shape on 18 November 2026: one base, with each fix measured on its own, in a file of its own. A set that the file cannot show to be exact is still shown, marked as estimated.
What the validator will hold:
Evidence
Text only. On #22, 215 Python tests and 82 node tests pass, unchanged. Acceptance cases F1–F8 (section 16.11) are written to become tests before the code.
Merge Danger
Door: two-way. A new section and six glossary lines. No format, code or test changes.
Blast radius: none for readers of
sentier-diagnostics/1. Once agreed, it decides the shape of a new format,sentier-diagnostics-fixes/1, and the work in sentier-bafu (the producer and the page).Based on #22 (
step-ranges): noise per state and the matrix's"=", which #24 builds on. This PR stays the text Manuel approved. #24 changes it where the validator decided:{fixes, kind, reach, largest};requires, added items and a built set'sstate;#24 also adds the pointer from section 3.
Reviewer: Manuel, for the text. Laurenz is asked only when the whole stack is done.
🤖 Generated with Claude Code