diff --git a/workplans/CUST-WP-0074-qualified-wait-states.md b/workplans/CUST-WP-0074-qualified-wait-states.md
index e0f8a83..6ef2c9c 100644
--- a/workplans/CUST-WP-0074-qualified-wait-states.md
+++ b/workplans/CUST-WP-0074-qualified-wait-states.md
@@ -103,13 +103,17 @@ The workplan-level `depends_on` (C-20) is unchanged. Task-level
 
 ```task
 id: CUST-WP-0074-T01
-status: todo
+status: progress
 priority: high
 state_hub_task_id: "82e9522b-bb69-52f4-b182-13ddfa8cd56e"
 ```
 
 Owner: the-custodian.
 
+2026-09-28: proposal committed — standard `11e6202` (status `proposed`),
+convention edit in the same commit, ralph-workplan spec `abea4cc`.
+Remaining: founder acceptance, then set the standard to `accepted`.
+
 - `canon/standards/task-wait-qualifiers_v0.1.md`: the shape above, the
   six rules, the derived-state names, and the satisfaction rule cross-
   referenced to `coordination-engine/spec/coordination-model-v0.2.md` §5.
@@ -131,11 +135,11 @@ priority: high
 state_hub_task_id: "e5a05f83-1db5-59a7-8cae-095237f50b7d"
 ```
 
-Owner: state-hub. This task is the handoff and its acceptance; the
-implementation lives in a `STATE-WP` workplan whose id gets recorded in
-`depends_on` here once it exists.
+Owner: state-hub. Founder 2026-09-28: implement directly from this plan,
+no delegated `STATE-WP` workplan — keep the layer count down while getting
+a grip on exactly this. Receipt (commits, checks, tests) is recorded here.
 
-Requested, by hub message to `state-hub`:
+Requested:
 
 - C-20 reads task-block `depends_on` (workplan and task ids) and writes
   `workplan_dependencies` rows with the waiting task as the from side —
@@ -157,13 +161,20 @@ fields answer for `CUST-WP-0074-T05` below.
 
 ```task
 id: CUST-WP-0074-T03
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "87711ade-f9f8-5e7f-9c15-025e5c235b35"
 ```
 
 Owner: coordination-engine.
 
+**Done 2026-09-28** (founder: implement directly, no delegated workplan).
+Spec edits committed in coordination-engine `354e800`, not pushed:
+`coordination-model-v0.2.md` §5 gains `kind: decision` and task-scope
+`depends_on`; `cross-owner-wait-mode-v0.1.md` entry 1 now keys on
+task-block `depends_on`, prose is a fallback until T05, and the Act
+section states that a human gate is never leased or woken.
+
 - `spec/coordination-model-v0.2.md` §5 gains commitment `kind: decision`
   for Case B, obligor = the named human or decision id, satisfaction =
   decision resolved. Case A is the existing `kind: completion`.