Design 47: the node record rides in the node's own have key (issue 1126, ADR 0555 §3)

03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md

@@ -678,8 +678,8 @@ backup holder backs up nothing, and the have says so.
   input from the bus with its own credential and nothing else (ADR 0547 §2, ADR 0549 §3):
   - **placement**, the indexer's state `placement`, one key `placement.<node>` read at each catalogue merge from
     the node's placement file and said by `placement-changed` (ADR 0549 §2);
-  - **the node records**, the node-engine's state `records`, one key `record.<node>` written by that node's own
-    agent and said by `node-record-changed` (ADR 0555 §3);
+  - **the node records**, each in its node's own have key `<node>.node`, written by that node alone and heard as
+    the key's change (ADR 0555 §3);
   - **the manifests**, the indexer's `modules.<module>` and its manifests by digest, or the digest the composing
     node's want names where it runs another build; the private network's manifest comes with mesh-sdk;
   - **the config values**, mesh-config's resolved state, the composing node's slice alone for a node agent.