diff --git a/workplans/GH-WP-0003-statute-v08-amendment-set.md b/workplans/GH-WP-0003-statute-v08-amendment-set.md
index 123039d..c4d6f9e 100644
--- a/workplans/GH-WP-0003-statute-v08-amendment-set.md
+++ b/workplans/GH-WP-0003-statute-v08-amendment-set.md
@@ -136,7 +136,7 @@ Place it in the statute where §8's three-way split is stated.
 
 ```task
 id: GH-WP-0003-T06
-status: progress
+status: done
 priority: medium
 state_hub_task_id: "ecc01a7b-22df-5a9c-a29b-eb7559713ca7"
 ```
@@ -216,15 +216,31 @@ v0.8 and it goes to the assent round rather than being imposed.
 
 ## T06 status
 
-**Cut done, circulation open.** `net-kingdom/canon/standards/security-layer-model_v0.8.md`
-exists as `status: proposed` at `net-kingdom@66eeaba`. All eight amendments applied,
-plus a §15 entry, a §1 "what changed", a §16 reconciliation closing two questions and
-opening one, and a rewritten §14. Section numbering is unchanged.
+**Round closed 2026-09-09; publication handed to `net-kingdom`.**
+`security-layer-model_v0.8.md` remains `status: proposed` at `net-kingdom@64394e9`.
+The acceptance flip and publication are `net-kingdom`'s and it has confirmed it will
+run them on round close. `security-layer-model_v0.7.md` stays `accepted` and in force
+until then, unpatched.
 
-`security-layer-model_v0.7.md` stays `accepted` and in force. It is not patched.
+Four repositories returned text reviews — `access-engine` (four findings),
+`approval-engine` (one partial plus three), `ops-warden` (two findings and one
+agreement), and `net-kingdom` (§17 confirmed, §11 corrected in place at `da7747d`).
+All are dispositioned in `docs/conformance/2026-09-06-v08-assent-round.md`.
 
-Remaining under T06: the assent round, and recording the returned dispositions. Two
-repositories carry a cost in this version and their review matters most —
-`ops-warden` acquires a non-conformant `unknown` cell under A8, and `approval-engine`
-acquires an issue-time digest obligation under A1/A5. Acceptance is `net-kingdom`'s
-publication step once the round closes.
+Nine corrections landed in the text during circulation, listed as §15 items 12–20. Two
+rulings were substantive enough to carry their own records:
+
+- **`GH-DEC-2026-010`** — a PEP must be able to *attribute* a decision to
+  `access-engine`, and obligation 2's digest test does not discharge obligation 1.
+  Fail-closed protects against a decision point that is absent, not against one that
+  lies. Carried as a declared §13 gap with `access-engine` as owner.
+- **`GH-DEC-2026-011`** — `ops-warden`'s asked-for transitional `unknown: fail_open` is
+  **declined**; §13.1 records a dated classification-coverage figure beside each stance
+  instead. Also settles that a map must enumerate its axis and that an `absent` scope is
+  distinguishable from an `unknown` one — closing the §16 question this version opened.
+
+**`kings-guard` and `audit-core` did not return a review.** §14 records that as *not
+claimed*. The sections they were asked to attack — §9.5's criteria-grounding clause and
+§12's step-four paragraph; §11's emission-guarantee wording — carry no assent from the
+repository best placed to test them. That is a gap in the round, not a defect in the
+text, and it does not block publication.