 jschoubben
|
37a5ab8f1c
|
A node that runs a module of policy record with no want yet is asked like any other, not treated as one that never ran it (issue 1906 D4)
|
2026-10-24 16:43:01 +02:00 |
|
|
jschoubben
|
e7a3ff1e7e
|
The record policy is the one the controller holds beside the composition, the operator's own choice included; pin mesh-sdk 64a502d (issue 1906 D4, ADR 0539 §14)
|
2026-10-24 16:41:58 +02:00 |
|
|
jschoubben
|
04c2c60f02
|
The assigner acts on answers: a release writes the held want again, a backup answer goes into the node's want, a record move waits for its yes, a restore answer sets a data module back (issue 1906 D4)
|
2026-10-24 16:37:37 +02:00 |
|
|
jschoubben
|
0df20b5d77
|
The assigner's seventh rule: a want names the digest of its composition and waits for it; a revision at the same fingerprint is a new want; the node's own want (issue 1906 D2, ADR 0539 §6)
|
2026-10-24 16:33:48 +02:00 |
|
|
jschoubben
|
204a59dab4
|
The assigner asks whether to restore a data module whose held fingerprint failed its health check, and raises the condition for a held fingerprint (issue 1906 D3)
|
2026-10-24 16:26:20 +02:00 |
|
|
jschoubben
|
024a3787da
|
End the assigner's comparison with the send: the controller sends nothing to compare with, so the differences bucket is kept read-only (issue 1906 D5, ADR 0539 §8)
|
2026-10-24 16:20:43 +02:00 |
|
|
jschoubben
|
97b42e3f0d
|
Name in every composition, by machine, those that could run a moved or added module and are not assigned it and those whose grants alone the change alters, as not judged, as ADR 0537 clause 1 asks (issue 1297)
|
2026-10-23 16:29:57 +02:00 |
|
|
jschoubben
|
77af82cfa2
|
Keep the asks state and write the ask about a held fingerprint, so the view's and the teller's read of mesh-delivery-assigner.asks is granted and has something to answer (issue 1297, review round 1 item 1; ADR 0528 clause 6)
|
2026-10-23 16:11:07 +02:00 |
|
|
jschoubben
|
d7ba5aa91e
|
Compare each node's want with the fingerprint of the build the controller sends it, explaining a difference by the rule that holds the want back or saying it unexplained (issue 1297, subtask B5a; ADR 0528 clause 4)
|
2026-10-23 15:30:31 +02:00 |
|
|
jschoubben
|
016385751d
|
Write each node's want by the six rules, the canary the first online node by name, and hold a fingerprint whose health failed with its nodes set back, so R5's wants can be compared with what the controller sends (issue 1297, subtasks B4a-B4b; ADR 0429 §6, ADR 0528 clauses 1 and 3, ADR 0435 §3)
|
2026-10-23 15:29:57 +02:00 |
|
|
jschoubben
|
d8599855e1
|
Compose the machines a change touches, from the trunk's and the change's manifests and the controller's assignments on the bus, and write the verdict under the checker's key; what needs the facts snapshot is said as not judged (issue 1297, subtasks B3a-B3c; ADR 0446 clauses 1-3, ADR 0528 clause 5, ADR 0482 clause 3 as R4g delivers it)
|
2026-10-23 15:25:22 +02:00 |
|