From e68d3a892e23919bd2f8e32420db4c24e93cd1b6 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 01:10:59 +0100 Subject: [PATCH 1/2] Answer A-456a and A-457a: a released build counts as reserved; the publish retries on the builder's own re-ask state --- .../01-to-be/47-milestones/G-22-lead-answers-2.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index cf66f2ba..23f46305 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1406,3 +1406,15 @@ the principle that settles it, cited as "design 47 G A-n". not a module or a fingerprint. The want says, in its words, that it waits for the entry of that fingerprint, so the wait is loud and read with `assigner_why`; that sentence of A-462 about the indexer's tool is withdrawn. (From the develop of A-462.) +- **A-456a** (A-456; principles 3 and 7) A released build counts as reserved: the build step passes a reserving build + whose fingerprint has a reservation or a released version. The builder knows the second from its own record of the + `version-released` it wrote for that fingerprint; where that record keeps no fingerprint today, the builder keeps + it there (its own state), never asking the catalog. (From the develop of A-456: the reservation is deleted at + release, so a rerun of a released build's step failed "no version reserved".) +- **A-457a** (A-457; principles 7, 1 and 11) "The builder's own work queue" is no new stream and no new process: the + publish item is a re-ask in the builder's own re-ask state, the mechanism `builder_reserve_done` and publish-again + already queue on, consumed by the builder's one process. The value carries its tries and its next try; a failed or + unanswered publish is written again with tries plus one and a pause of `publish-pause` doubled per try up to + `publish-pause-max`, and after `publish-tries` tries it ends loudly (log, condition) and stays readable in the + builder's tools; all three are settings with defaults (30 s, 30 min, 8). (From the develop of A-457: a work-queue + stream would need a `bus` restating the builder's whole account, or a second process.) -- 2.54.0 From 2ff96d1b7e52c75d7490d7871bfaf620d50f85c6 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 01:11:09 +0100 Subject: [PATCH 2/2] Answer A-461a: another node's module is laid from the assignment's placed build --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 23f46305..c449c3a7 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1418,3 +1418,7 @@ the principle that settles it, cited as "design 47 G A-n". `publish-pause-max`, and after `publish-tries` tries it ends loudly (log, condition) and stays readable in the builder's tools; all three are settings with defaults (30 s, 30 min, 8). (From the develop of A-457: a work-queue stream would need a `bus` restating the builder's whole account, or a second process.) +- **A-461a** (A-461; principles 7 and 1) "The build its want names" for another node's module is read from what the + composer already holds for every node: the assignment's placed build of that module on that node (absent meaning + the newest delivered, as the assignment says). The composer watches no other node's wants. (From the develop of + A-461: the composer holds only its own node's wants.) -- 2.54.0