docs(plans): lead decision 57, schema v3a accepted

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-04 22:03:02 -05:00
parent 29daa48216
commit c9ff79c802
2 changed files with 18 additions and 0 deletions
@@ -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.