diff --git a/WORK-RECORDS.md b/WORK-RECORDS.md
index 29de0bb..1d2fb8e 100644
--- a/WORK-RECORDS.md
+++ b/WORK-RECORDS.md
@@ -18,7 +18,7 @@
 | workplan | TEN-WP-0007 | finished | — | workplans/TEN-WP-0007-guardrail-production-rollout.md |
 | workplan | TEN-WP-0008 | ready | — | workplans/TEN-WP-0008-staged-promotion-onboarding.md |
 | workplan | TEN-WP-0009 | ready | — | workplans/TEN-WP-0009-postgres-production-store.md |
-| workplan | TEN-WP-0010 | ready | — | workplans/TEN-WP-0010-mutable-grouping.md |
+| workplan | TEN-WP-0010 | finished | — | workplans/TEN-WP-0010-mutable-grouping.md |
 | task | ADHOC-2026-07-24-T01 | done | — | workplans/ADHOC-2026-07-24.md |
 | task | TEN-WP-0001-T01 | done | — | workplans/TEN-WP-0001-statehub-bootstrap.md |
 | task | TEN-WP-0001-T02 | done | — | workplans/TEN-WP-0001-statehub-bootstrap.md |
@@ -65,4 +65,4 @@
 | task | TEN-WP-0010-T02 | done | — | workplans/TEN-WP-0010-mutable-grouping.md |
 | task | TEN-WP-0010-T03 | done | — | workplans/TEN-WP-0010-mutable-grouping.md |
 | task | TEN-WP-0010-T04 | done | — | workplans/TEN-WP-0010-mutable-grouping.md |
-| task | TEN-WP-0010-T05 | todo | — | workplans/TEN-WP-0010-mutable-grouping.md |
+| task | TEN-WP-0010-T05 | done | — | workplans/TEN-WP-0010-mutable-grouping.md |
diff --git a/workplans/TEN-WP-0010-mutable-grouping.md b/workplans/TEN-WP-0010-mutable-grouping.md
index 38fcf36..3331c0e 100644
--- a/workplans/TEN-WP-0010-mutable-grouping.md
+++ b/workplans/TEN-WP-0010-mutable-grouping.md
@@ -71,7 +71,7 @@ about to start going stale, and does not know it.**
 
 ```task
 id: TEN-WP-0010-T01
-status: todo
+status: done
 priority: high
 state_hub_task_id: "374626c0-5dad-458f-a595-e4e06fe47017"
 ```
@@ -104,6 +104,12 @@ as a real option, with the exception path it would then require.
 
 Implementation proceeds in parallel per the note above.
 
+Marked done because this task was to *propose* and record status, both of
+which are complete. **Ratification itself is outstanding and is canon's, not
+ours** — until `net-kingdom` rules, point 4 binds this repo's own behaviour but
+not the fleet's. If they choose the frozen reading instead, the mutation built
+here stays correct and the guardrail exception path becomes a new workplan.
+
 ## T02 - Find out who parses the grouping segment
 
 ```task