Answer A-197: the node-engine raises its own findings, the watchman reads none of its state

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 24df2be69a
commit 9adfad1108
1 changed files with 5 additions and 0 deletions
@@ -71,3 +71,8 @@ the principle that settles it, cited as "design 47 G A-n".
 - **A-196** (§553 with A-91; principle 7; the operator, 2026-11-09: merges need no approval) An empty status makes a
  step `optional`, as §553 says, except the approval step: a policy that names no approval status asks the operator
  nothing, as A-91 says; only a policy that names approval asks for it.
+- **A-197** (ADR 0596, A-192, A-149; principles 1, 3 and 7) What only the node-engine knows of itself it raises as its
+  own findings through its finding writer: a have's failed or removed phase and its detail, its kept-data findings,
+  an unreachable tunnel, and every part of its health report (machine network, rewritten network, machine units,
+  relogin needed, directory used as found, node account fallback). The watchman stops reading `node-engine.have` and
+  `mesh-host.health` and raising those; it keeps only what it sees across parts.