diff --git a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md
index e5aa88c6..978dffdd 100644
--- a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md
+++ b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md
@@ -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.