Answer A-341: a zfs device's finding in the writer's key form

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-13 09:16:08 +01:00
parent 20a04f0226
commit 253c18c693
1 changed files with 4 additions and 0 deletions
@@ -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.<pool>.<device>` (the pool's own state: `zfs.<pool>.pool`), kind `not-online`, its subject scope
+  `module`, id `zfs`, on the node; `<device>` 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.