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 9187bf39..a22f4fae 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
@@ -679,3 +679,23 @@ the principle that settles it, cited as "design 47 G A-n".
   (a resource's own `MESH_NODE` is refused by the manifest validator, so the mesh's value is the only one). The zfs
   follower's writer and its `node-service-manager` calls then name the node; no new reference form and nothing special to
   the keeper.
+- **A-343** (§50, §494, §697; principles 5, 7; the operator, 2026-11-13: G's order put right, readers first) A third reader
+  release goes before G: one delivery group of mesh-sdk and mesh-delivery that carries exactly the readers of the seven
+  forms today's manifest validator refuses in G's manifests (R1 invokes `seat:<seat>.accept.<queue>` and
+  `seat:<seat>.<stream>.<kind>`; R2 reads `seat:<seat>.<state>`; R3 `last-per-subject`; R4 `objects-max-mib`; R5
+  `mesh-host-findings`; R6 the old `objects` section of gitea and distribution; R7 a process's `bus.consumes`), built from
+  mesh-sdk main after the revert (27da9491). The node-engine is rebuilt with the release's mesh-sdk, so it states
+  `word:streams.last-per-subject`. Nothing accepted on main today is refused after it: f1-circuits and link2pay stay as
+  they are, named in the whole-run test. How it is checked: today's validator, rebuilt with the release, accepts all 193 of
+  G's manifests and every trunk manifest it accepts today; delivered and reached on every node before G is asked again.
+- **A-344** (A-343; §601, A-128; principle 3) The release reads each form with G's check of it (a `seat:` name that names
+  no seat, queue, stream or state of that seat is refused, as G refuses it), never the form alone; no trunk manifest uses
+  these forms, so nothing on main is refused for them.
+- **A-345** (A-343, §584, §627; principle 7) Before G's merge the foundation list stays as it is; the two old forms of
+  gitea, distribution and the node-engine (bus state in `requires`, the old `objects` section) are accepted for exactly
+  those modules until G puts them on the list.
+- **A-346** (A-343, §600, §601; principle 7) The release changes no grants code: until G is delivered the grants part
+  keeps its reading; G's own grants part is delivered first within G (§90).
+- **A-347** (A-343, §714, §715) G's take-in is one revision of its group, so the acceptance of the release is the
+  all-of-G run (G's 193 manifests with G's 65 seat definitions), not the live per-member verdicts of before.
+- **A-348** (corrects §703's sentence; A-343) The second reader release did not carry `last-per-subject`; the third does.