Answer A-339: zfs's findings take G's writer over its keeper

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-13 09:08:48 +01:00
parent a7004d5e2a
commit 325bf80f19
1 changed files with 6 additions and 0 deletions
@@ -659,3 +659,9 @@ the principle that settles it, cited as "design 47 G A-n".
 - **A-338** (A-335, ADR 0233; principle 7; the operator, 2026-11-13 about 03:50 CET: "it's a poc") The two trunk manifests
  the manifest validator refuses once they change, for a written directory with no data declared, declare it in G's
  change: f1-circuits' `cache` and Link2Pay's `logs`, both class `cache`.
+- **A-339** (G §383, §384, §387; design 42 zfs-owns-zfs A-32, A-37, A-39, A-41; principles 1, 7) The zfs module's
+  findings take G's form through the bus path it already has: its keeper's closed list gains exactly what G's generated
+  findings writer needs (the publish of `finding-written` on its stream `zfs-findings`, and a hear of
+  `mesh-conditions.findings-asked`), and the root follower runs G's writer over the keeper; its manifest gains the
+  `finding-events` stream and that `consumes`. The follower keeps writing its findings, since it is the part that sees
+  them; nothing else of the keeper's list widens.