diff --git a/03-DESIGN/01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md b/03-DESIGN/01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md
index 68fd9f68..314df074 100644
--- a/03-DESIGN/01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md
+++ b/03-DESIGN/01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md
@@ -39,7 +39,7 @@ settles it (`00-META/principles.md`), cited as "design 42 zfs-owns-zfs A-n". The
 - **A-9** (Q-9, §30; principle 7) When the module leaves a node, its kept data (the states `applied`, `schedule` and
   `findings`, the ledger `snapshots`, the events stream) is kept as every module's kept data is on leaving; a return
   finds its scheduled ZFS snapshots' records.
-- **A-10** (Q-10, §27; principle 7) The findings stream is the one design 47 G §383 defines for every observer:
+- **A-10** (Q-10, §27; principle 7; corrected by A-32) The findings stream is the one design 47 G §383 defines for every observer:
   `zfs-findings`, its events `finding-written.*`, `finding-cleared.*` and `findings-stated.*`, kept 7 days and
   16 MiB, said by the writer generated from the seat `mesh-conditions`' definition; the module declares it as §383
   says and builds nothing of its own for it.
@@ -107,3 +107,9 @@ settles it (`00-META/principles.md`), cited as "design 42 zfs-owns-zfs A-n". The
 - **A-31** (§21, §22, §28, A-20, met in develop; principles 1 and 7) The scheduled run reads the ledger as it writes
   it, through its own module's tools: its process bus also invokes `zfs.zfs_snapshots_schedule`, whose answer holds
   the ledger's entries (§28), and the run takes a kind's last entry and the entries to prune from that answer.
+- **A-32** (corrects A-10, §27, met in develop; principles 2 and 7) The writer A-10 names is not on mesh-sdk's main: it
+  is built only on design 47 G's branch, a milestone not yet delivered. The follower says its findings in its own
+  state `findings`, keyed and written as every observer on main writes its findings today, and declares no
+  `zfs-findings` stream; G's change of §387 writes that stream into every module that declares a state `findings` on
+  main when it lands, the zfs module among them. Read before A-10 was given: nothing; the lead now reads what an
+  answer names first (playbook 07, step 0b).