From 253c18c69380fb6e43597d86a5aaf50de11277d8 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 13 Nov 2026 09:16:08 +0100 Subject: [PATCH] Answer A-341: a zfs device's finding in the writer's key form Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 58ae2622..77054c08 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -670,3 +670,7 @@ the principle that settles it, cited as "design 47 G A-n". does, and the grants part gives that process's account the hear and the consumer of exactly those events, as G1 gives the publish. The zfs keeper names `mesh-conditions.findings-asked` there. "Exactly what G's writer needs" is its three events on the module's `finding-events` stream: `finding-written`, `finding-cleared`, `findings-stated`. +- **A-341** (A-339; design 42 §27; G's findings writer; principle 7) Under G's writer a zfs device's finding is scope + `module`, id `zfs..` (the pool's own state: `zfs..pool`), kind `not-online`, its subject scope + `module`, id `zfs`, on the node; `` is the device's own name, the last element of its path. §27's one finding + per device not online stands; only its key takes the writer's form.