diff --git a/docs/spec-change-proposals.md b/docs/spec-change-proposals.md
index 49c1e0f..50a1363 100644
--- a/docs/spec-change-proposals.md
+++ b/docs/spec-change-proposals.md
@@ -1,6 +1,8 @@
 # MAS v0.1 spec change proposals (from MAS-WP-0002/0003)
 
-Status: **draft for review**. These are proposals against
+Status: **accepted by the founder (2026-10-18)**: SCP-1 to SCP-7 as written
+below, including the decisions recorded under SCP-2 and SCP-6.
+Implementation is tracked in MAS-WP-0005. These are proposals against
 `mas-v0.1-spec/`. The spec bundle stays unchanged until they are accepted,
 because `mas_conformance/` and `mas_core/schema/` are vendored copies and
 the tests check them for drift. Evidence references point to
diff --git a/workplans/MAS-WP-0005-spec-errata-v0-1-1.md b/workplans/MAS-WP-0005-spec-errata-v0-1-1.md
index b9576d3..bfa77e0 100644
--- a/workplans/MAS-WP-0005-spec-errata-v0-1-1.md
+++ b/workplans/MAS-WP-0005-spec-errata-v0-1-1.md
@@ -26,7 +26,7 @@ copies, the fixtures and the implementation together.
 
 ```task
 id: MAS-WP-0005-T01
-status: progress
+status: done
 priority: high
 state_hub_task_id: "10c0433a-9b25-5b62-987f-2be7e9d49df2"
 ```
@@ -60,8 +60,11 @@ SCP-6 split rules), and record which proposals are accepted.
   (`alternate_syntax: {resource: true, interaction: true}`). Matching
   order: interaction (`---MODE` at the end, enabled mode) first, then
   resource (`TYPE--ID`). IDs must not contain `---` when the interaction
-  stand-in is enabled. Remaining T01 items: confirm SCP-1, SCP-3, SCP-5
-  and SCP-7 as written.
+  stand-in is enabled.
+- 2026-10-18: SCP-1, SCP-3, SCP-5 and SCP-7 confirmed as written. All seven
+  proposals are accepted, so T01 is done. T02 implements the v0.1.1
+  errata (SCP-1, SCP-2 (a), SCP-3, SCP-5, and the SCP-7 recommendation);
+  T04 implements SCP-6 and the SCP-7 statute field for v0.2.
 
 ## v0.1.1 errata