diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md
index 5258cc09..95133f94 100644
--- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md
+++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md
@@ -426,3 +426,11 @@ the principle that settles it, cited as "design 47 G A-n".
   only within the state's bound per value; an answer over it, a check's or a run's alike, is kept as the object
   `output.<ask>` in the module's outputs store and the key names it, and every reader (the checker, the asker) reads
   the answer from the key or the object it names. No step ends passed in one place and failed in another.
+- **A-291** (A-254, A-290; principle 7, and code shared between modules lives in the SDK) A process receives a seat
+  verb's chunked answer through one helper of mesh-sdk's process package, which subscribes to the call's chunks
+  before it asks and answers the whole body; the checker, the indexer, the assigner and the recovery keeper (whose
+  own receive moves into it) read a step's answer kept as an object through it.
+- **A-292** (§590, issue 1975; principles 1 and 3) The node-engine's first statement keeps the bootstrapped seats (no
+  'not yet'); every later change is said as `manifest-reads-changed` at once. A say the bus does not take is said
+  again within the same link through the SDK's bus retry until the bus takes it, and each failed attempt is written
+  to the engine's journal with the event's name; the held-for-the-next-link form stays only for a link that is lost.