Answer A-28: own followers through a reader, a single ask through the writer

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
2026-11-11 22:00:05 +01:00
parent 201e998418
commit dca4bc973e
1 changed files with 4 additions and 0 deletions
@@ -106,3 +106,7 @@ names the principle that settles it, and is cited as "design 47 G A-n".
 - **A-27** (A-26, A-16; principle 7) The tool runner's first views follow A-26 too: `firstview` builds a
  `views.ProcessReader` over the runner's bus connection and adopts its followers, so the reader raises their findings;
  the runner's `bus.Conn` gains one accessor for its JetStream, its one place (A-16).
+- **A-28** (A-26, A-22, §687; principle 7) A part's own follower (mesh-config, mesh-vault) is followed through a
+  `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.