Answer A-29: one mesh-sdk writer that observes from its own state

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
2026-11-11 22:01:05 +01:00
parent a1c77688ab
commit 2103f4479b
1 changed files with 4 additions and 0 deletions
@@ -110,3 +110,7 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  `views.Reader` holding the module's writer and adopted, as A-26. A single ask that is no follower (mesh-build-go's
  manifest ask, the tool runner's ask) writes and clears its `first-view-unanswered` finding itself through
  `Writer.Write` and `Writer.Clear` with the contract's `Finding`; mesh-sdk exports no helper for it.
+- **A-29** (§686, A-3; principle 7, shared code lives in mesh-sdk) A part whose findings are raised as they happen, not
+  judged afresh, uses one mesh-sdk form of the writer that observes from its own state: it seeds what it holds from the
+  state's keys before it starts, keeps them under its own lock, and its `Observe` answers them, so no part writes that
+  adapter (the watchman's copy moves there; the assigner, builder and indexer use it).