mesh-issues: a counter not started never starts without the knowledge base's answer, floor or no floor (review of #214)
mesh/merge-gate pass: builds mesh-issues, mesh-knowledge, records → novox; no bus step; every machine composes with the change as it did without (4 of 4 co…
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery delivered

This commit is contained in:
2026-10-11 12:44:45 +02:00
parent 2369098303
commit 1b7f79f761
3 changed files with 22 additions and 27 deletions
+4 -5
View File
@@ -207,9 +207,8 @@ sessions writing a record at once never take one number.
accepted, proposed, reserved or withdrawn; hq issue 488), the setting `decision-floor` or `research-floor`,
and the reservations kept. The first number handed out is one above. hq's folders are not read: the records
live in the knowledge base, and those folders empty when they leave hq (hq issue 426). When the knowledge base
does not answer (or holds none of the kind), the counter starts from the floor alone and the answer's
`warning` says it was not checked; with no floor either, the first reserve of a kind is refused and nothing
is spent.
does not answer (or holds none of the kind), the first reserve of a kind is refused and nothing is spent,
whatever the floor says: a floor raises the start, and never stands in for the knowledge base's answer.
- **Never at or below a number held**: each reserve asks the knowledge base again, and a counter that stands
below the highest number there is raised to it first, written only at the revision read. When the knowledge
base does not answer once the counter has started, the counter is used as it stands, and the answer's
@@ -284,8 +283,8 @@ the counter written without its revision check, it fails.
what the knowledge base holds — is `TestFortyReservationsAtOnceFromTwoInstancesGetFortyDistinctConsecutiveNumbers`
on the same bus, with the knowledge base played by the test, and the tests in `reserve_test.go`: the start above
the knowledge base, the floor and the reservations kept, a counter behind the knowledge base raised, a refused
reserve spending nothing, the first reserve refused while neither the knowledge base nor a floor answers, the
floor alone starting it with a warning, a kind held none of being no answer, hq's folders never read, and a
reserve spending nothing, the first reserve refused while the knowledge base does not answer, even with a floor
set, a kind held none of being no answer, hq's folders never read, and a
reservation that cannot be kept leaving its number spent.
The import is tested over `testdata/hq`, copies of seven real reports of hq chosen for their shapes (a