Answer A-47: the node-engine's entry reads and kept entries

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 22:39:04 +01:00
parent d50a593d68
commit da5c034928
1 changed files with 6 additions and 0 deletions
@@ -180,3 +180,9 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  `versions` (`builder_versions`), as its MAJOR.MINOR (mesh-sdk `0.1`), and `0.1` for a module with none published.
  The developer reads it through `builder_versions` and writes it into every manifest of every repository in the
  group, one commit per repository, listing the values in the commit.
+- **A-47** (§421, §683, §698, ADR 0593 §6; principle 7) The node-engine reads by fingerprint only (§421), so it follows
+  no branch: it uses the shared follower's entry cache alone (`Entries`, A-5, A-15) over its own `entry` calls on its
+  link session. It keeps the entries and wants of §683 in its `composed-<node>` bucket, keys `entry.<fingerprint>` (the
+  entry as `entry` answers it) and `want.<module>` (the want as `wanted` says it), beside the composition. Its other
+  users of `compose/frombus` keep that reader until their own lines move them; only the node-engine's own reads of the
+  indexer's and builder's states go in this change.