Design 47: the assigner's acceptance test names its six rules, as ADR 0547 §4 leaves them; the bus node follows the controller's list until the third milestone, for hand-back; placement stays where it is for now (issue 1126)

2026-10-26 02:59:58 +01:00
parent d70791ddee
commit f1c50d3e01
1 changed files with 3 additions and 3 deletions
@@ -193,7 +193,7 @@ there is three milestones, one issuer of each key at every moment (ADR 0547 §11
   lists are equal but for users placement no longer names, so it waits until the enrolment users and the persons
   have records on the bus, and the second milestone waits for it (ADR 0547 §8, §11).
 2. **Nodes compose** (issue 1126): each node agent composes its own modules; no node applies a composition made
-   elsewhere but the bus's user list until `take-over`.
+   elsewhere but the bus's user list, which the bus node keeps able to follow until the third milestone so `hand-back` has a list to return to.
 3. **Nothing is left with the controller** (issues 1126, 774): the vault mints bus accounts, the grants part
   writes grants, the try is the checker's own verb, placement and the signing key are where the operator's
   answers put them, and the controller's lease is handed to a holder that is no controller once every other job
@@ -826,7 +826,7 @@ What the build proves before this design is implemented (research 055's directio

 1. A feature across the controller and the catalogue with a new seat verb is delivered as one group, with no
   `after:` line, one composed check and one Approve: its merges move one source revision, each module it changes
-   is built once, and every want naming one of those fingerprints is written by the assigner's seven rules, with
+   is built once, and every want naming one of those fingerprints is written by the assigner's six rules, with
   no order written by anyone.
 2. An SDK change and a Go module using it are delivered as one group.
 3. A data module is backed up by its node's backup seat before the node agent applies a new fingerprint of it,
@@ -851,7 +851,7 @@ What the build proves before this design is implemented (research 055's directio
    newer fingerprint once its rules hold, a fingerprint nobody wants any more is never applied, and nothing is
    released by a person or held in the gate.
 12. No table in the controller's store holds builds, deliveries or assignments: builds are the builder's keys,
-    wants the assigner's, haves the node agents', and placement the controller's assignments bucket.
+    wants the assigner's, haves the node agents', and placement, for now, the controller's assignments bucket (where it lives is the operator's choice, issue 1126).

 Tests 1 to 12 are stated as they hold from release 6. Tests 1, 3, 7, 8, 9, 10 and 11 were first proved by
 milestones 1 to 5 in the shape of their time, the controller's plans and what it sent (the milestones table keeps