From da5c034928814c35256a97f91798631b7ff8738b Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 22:39:04 +0100 Subject: [PATCH] Answer A-47: the node-engine's entry reads and kept entries Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md index 94141c57..820327c5 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md @@ -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-` bucket, keys `entry.` (the + entry as `entry` answers it) and `want.` (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.