novox/hq
18
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Design 47: a placed node's want says self and names no composition; a yes names the composition allowed (issue 1126, ADR 0547 §2, §3)
mesh/delivery closed: a newer head of the same pull request
Details
mesh/check failed: ace: novox/mesh-catalog#505 does not merge into the trunk: files in conflict: .gitignore | 495d740d5ffc on d698942b1d56 | unit 1245…

Browse Source
This commit is contained in:
jschoubben
2026-10-26 19:17:48 +01:00
parent df4ff3d039
commit 495d740d5f
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md
+4 -1
View File
@@ -749,7 +749,10 @@ backup holder backs up nothing, and the have says so.
and nothing is asserted (ADR 0547 §5). and nothing is asserted (ADR 0547 §5).
- **The want names the build.** A want `want.<node>.<module>` names the fingerprint, the artifact's digest, the - **The want names the build.** A want `want.<node>.<module>` names the fingerprint, the artifact's digest, the
source revision and whether the module holds data; the node's own want `want.<node>.node` names the node source revision and whether the module holds data; the node's own want `want.<node>.node` names the node
(ADR 0547 §2). (ADR 0547 §2). A want to a node the catalogue places says so: it carries `self` and names no composition,
since the node composes it; every other want still names the one composition it allows, so nothing written
before (the controller's bus upgrade among it) reads a want differently. A person's yes to a move the node
judged is written into the want as `yes`, the digest of the composition allowed (ADR 0547 §3).
- **The apply, one module at a time.** At its first start the node agent takes the declaration it kept last as - **The apply, one module at a time.** At its first start the node agent takes the declaration it kept last as
what each module runs and writes each have. Then it applies a module only when its want's fingerprint what each module runs and writes each have. Then it applies a module only when its want's fingerprint
differs from what runs or the composition it composed differs from the one it runs, and only that module, differs from what runs or the composition it composed differs from the one it runs, and only that module,