From eb061c76034cc1430fdb26388de71f0d5776bc7c Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 22:57:04 +0100 Subject: [PATCH] Answer A-65: mesh-knowledge's findings go through the writer Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 3 +++ 1 file changed, 3 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 8ccedd8c..8b6d0c99 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 @@ -254,3 +254,6 @@ names the principle that settles it, and is cited as "design 47 G A-n". says no event; an unprotected snapshot's restore refuses nothing further; each chunk is acknowledged by a request, since the runtime answers only calls with a reply. One change: `snapshots-filling` takes an existing scope word, scope `module`, id `nats.snapshots`. +- **A-65** (§387, §529; principle 1, a module's data lives on the bus) mesh-knowledge's findings go through the writer + like every observer's: it gains the `finding-events` stream and a writer over the `findings` state it already + requires, and its findings no longer live in its database.