diff --git a/docs/SESSIONS.md b/docs/SESSIONS.md
index 29c01eaa..4028eba9 100644
--- a/docs/SESSIONS.md
+++ b/docs/SESSIONS.md
@@ -486,3 +486,4 @@ are never rewritten or removed; corrections are new entries.
 2026-10-04 | dewey | Slice 1 S5 (#1522), row 40 design | Design note agents/dewey/work/wui/SLICE1-VIEWS.md from data model, addenda A+B and schema v3; questions Q1-Q5 sent to Sage; no code, no commit; build waits for S4.
 2026-10-04 | rocko | Slice 1 S2 #1519 row 37 | Started after schema v3 pin verification and Sage authorization; fixture credentials only; Darkwing review and Sage commit pending.
 2026-10-05T02:58:34Z | Sage (T3 Claude Code, thread 1ef1e4f8) | slice 1 SR runbook, S5 rulings | docs/guides/slice-1-identities.md drafted for Darkwing's review (row 35); lead decision 56 accepts Dewey's Q1-Q5; Rocko started row 37
+2026-10-05T03:03:02Z | Sage (T3 Claude Code, thread 1ef1e4f8) | schema v3a | Darkwing's v3a (29daa482) rerun matched on Node 26; lead decision 57; row 37 note
diff --git a/docs/plans/2026-09-26_lead-decisions.md b/docs/plans/2026-09-26_lead-decisions.md
index afcc6217..34ea6ba9 100644
--- a/docs/plans/2026-09-26_lead-decisions.md
+++ b/docs/plans/2026-09-26_lead-decisions.md
@@ -935,3 +935,20 @@ which stay with him. Each item names who decided it and what happened.
     - Q5: S5 also fixes `escalating` staying set after a throw, and a
       takeover followed by Enter in one chunk, because both sit in files
       S5 owns. The freeze-ordering test stays in DEFERRED.
+57. **Schema v3a accepted (2026-10-04).** Source: Darkwing, commit
+    29daa482, `agents/darkwing/work/slice1-proto/schema-v3a.sql` (sha256
+    d55e41fd…). Sage's rerun on Node 26.8.1 matched. Row 37 (S2) builds
+    from v3a instead of v3.
+    - Both Q3 rules from decision 56 are triggers, and the broker also
+      sets the fields. Every `task.*` event names its task in `subject`.
+      The `task.created` body's `request` names a `human.input` event
+      already in the bus, from the same business.
+    - The `requirement` check in the same trigger stays, beyond what Q3
+      asked. REQ-TASK-1 already refuses a task without a requirement id,
+      and addendum A put that id on `task.created`. The trigger checks
+      the shape, and the broker checks that the id exists in the PRD.
+    - The tighter task ref pattern (`vikunja:<int>/<int>`, positive, no
+      leading zero) stays, and it now covers `decisions.task_ref` too.
+    - The broker, not a trigger, links `action.*` and `review.*` events
+      to a task, because the kind alone doesn't say when one is about a
+      task.