Answer A-65: mesh-knowledge's findings go through the writer

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 22:57:04 +01:00
parent c1d331da40
commit eb061c7603
1 changed files with 3 additions and 0 deletions
@@ -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.