diff --git a/WORK-RECORDS.md b/WORK-RECORDS.md
new file mode 100644
index 0000000..c79fbfa
--- /dev/null
+++ b/WORK-RECORDS.md
@@ -0,0 +1,18 @@
+# Work Records — maturity-engine
+
+> Generated by `statehub fix-consistency` (CUST-WP-0061-T04, work-record
+> stage 3). Do not edit by hand — edit the source file/block listed for
+> each record and re-run fix-consistency to refresh this index. Archived
+> workplans are omitted; closed decisions/intakes/engagements stay listed
+> so recently-resolved work is still visible. [auto]
+
+| Kind | ID | Status | Lane | Source |
+| --- | --- | --- | --- | --- |
+| workplan | MAT-WP-0001 | ready | — | workplans/MAT-WP-0001-netkingdom-security-layer-engine.md |
+| task | MAT-WP-0001-T01 | todo | — | workplans/MAT-WP-0001-netkingdom-security-layer-engine.md |
+| task | MAT-WP-0001-T02 | todo | — | workplans/MAT-WP-0001-netkingdom-security-layer-engine.md |
+| task | MAT-WP-0001-T03 | todo | — | workplans/MAT-WP-0001-netkingdom-security-layer-engine.md |
+| task | MAT-WP-0001-T04 | todo | — | workplans/MAT-WP-0001-netkingdom-security-layer-engine.md |
+| task | MAT-WP-0001-T05 | todo | — | workplans/MAT-WP-0001-netkingdom-security-layer-engine.md |
+| task | MAT-WP-0001-T06 | todo | — | workplans/MAT-WP-0001-netkingdom-security-layer-engine.md |
+| task | MAT-WP-0001-T07 | todo | — | workplans/MAT-WP-0001-netkingdom-security-layer-engine.md |
diff --git a/workplans/MAT-WP-0001-netkingdom-security-layer-engine.md b/workplans/MAT-WP-0001-netkingdom-security-layer-engine.md
index 809e42f..28a3b88 100644
--- a/workplans/MAT-WP-0001-netkingdom-security-layer-engine.md
+++ b/workplans/MAT-WP-0001-netkingdom-security-layer-engine.md
@@ -9,6 +9,7 @@ owner: grok
 topic_slug: netkingdom-security-layer-alignment
 created: "2026-08-29"
 updated: "2026-08-29"
+state_hub_workstream_id: "fdc711d0-bcb5-5e40-920c-d608f705f34f"
 ---
 
 # MAT-WP-0001 - Stand up maturity-engine on security-layer-model v0.7
@@ -49,6 +50,7 @@ Companion: `net-kingdom/SECURITY-COMPANION.md` v0.2.
 id: MAT-WP-0001-T01
 status: todo
 priority: high
+state_hub_task_id: "930d9cba-abf5-5982-8f7a-0f8afe518713"
 ```
 
 Add `layer.yaml` in the kings-guard no-contact shape, adapted for Engine/PIP,
@@ -76,6 +78,7 @@ reviewer can see there are no Tooling contacts and no PEP claim.
 id: MAT-WP-0001-T02
 status: todo
 priority: high
+state_hub_task_id: "a9b019c6-b518-59b1-913a-e47ed8fcc925"
 ```
 
 There is no implementation to update. Choose and record:
@@ -99,6 +102,7 @@ scaffold, and SCOPE's "no runtime" bullet is no longer the whole story.
 id: MAT-WP-0001-T03
 status: todo
 priority: high
+state_hub_task_id: "2b35f065-47fb-5daf-a68d-cf86b8b3d8d7"
 ```
 
 Implement the modeled concept:
@@ -123,6 +127,7 @@ demotion from recorded inputs, with no human in the compute path.
 id: MAT-WP-0001-T04
 status: todo
 priority: high
+state_hub_task_id: "18666e16-a882-571b-a6cc-dee4ddb938eb"
 ```
 
 Take statute §13's snapshot into this engine:
@@ -149,6 +154,7 @@ conforming, and notice has been sent.
 id: MAT-WP-0001-T05
 status: todo
 priority: medium
+state_hub_task_id: "496b98a6-4e28-5d96-a758-1aa8dde7596d"
 ```
 
 Take statute §13.1's inventory: every PEP-shaped consumer's published
@@ -170,6 +176,7 @@ surface-exists without implying ownership of actuation.
 id: MAT-WP-0001-T06
 status: todo
 priority: high
+state_hub_task_id: "1a606ac1-1b02-5b33-a8c3-79f6f45a841f"
 ```
 
 Publish the PIP claim shape `access-engine` consumes for a maturity
@@ -196,6 +203,7 @@ with the §9.6 bound stated next to the trail.
 id: MAT-WP-0001-T07
 status: todo
 priority: medium
+state_hub_task_id: "e476cc41-0a9d-59e5-b2e1-44f974997acd"
 ```
 
 Register at least two ladders owned by different repositories. The first