From 0afac8d52ec552c4386d7335632e3f77268b9978 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 05:40:13 +0100 Subject: [PATCH] Answer A-176: one mesh-sdk helper writes a process's consumer facts Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 5 +++++ 1 file changed, 5 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 f84a1013..07f4495c 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 @@ -663,3 +663,8 @@ names the principle that settles it, and is cited as "design 47 G A-n". `views.answers`, and the view says its own `answers` the same way; each follows the other's by mesh-sdk's `ProcessReader.Follow` (first view through the owner's tool, then its views family). That is the "event" A-172 and §431 mean; no own follower and no module-event adopt are added. +- **A-176** (A-166, §579, §76; principle 7; code shared between modules is in mesh-sdk) A process writes its durable + consumers' facts (stream, name, acknowledged sequence, pending, last event applied and its `at`, and when its oldest + unacknowledged message was delivered) into its module's own state `consumers` (history 1, a key per consumer) through + one mesh-sdk helper, after each message it applies; the runner and the indexer use it, and their tools read that + state.