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 314df074..6498f9a2 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
@@ -113,3 +113,11 @@ settles it (`00-META/principles.md`), cited as "design 42 zfs-owns-zfs A-n". The
   `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).
+- **A-33** (§20, met in develop; principle 3) A trim schedule set without its `trim-day` or `trim-time` runs no trim and
+  is said: the parse refuses it as one refused value (A-28), naming the missing value.
+- **A-34** (§24, A-18, met in develop; principle 7) A hand act's `why` and `by` are kept in its key of the state
+  `schedule`, which the run deletes once it acted, and its outcome is the event the act itself emits (§25); no new
+  event kind.
+- **A-35** (§21, §22, met in develop; principle 3 and the operator's "we may absolutely not lose any data") A kind's
+  keep count of 0 is that kind's `none`: none is taken, its existing scheduled ZFS snapshots are kept and a warning
+  names them; only a count above 0 prunes past it.