diff --git a/workplans/APPROVAL-WP-0004-exact-consume-source-provenance.md b/workplans/APPROVAL-WP-0004-exact-consume-source-provenance.md
index b9bc3fc..2fc6eef 100644
--- a/workplans/APPROVAL-WP-0004-exact-consume-source-provenance.md
+++ b/workplans/APPROVAL-WP-0004-exact-consume-source-provenance.md
@@ -4,13 +4,14 @@ type: workplan
 title: "Retain exact authenticated consume source provenance"
 domain: infotech
 repo: approval-engine
-status: active
+status: finished
 flavor: implementation
 owner: codex
 topic_slug: netkingdom
 created: "2026-10-16"
 updated: "2026-10-16"
 depends_on: []
+state_hub_workstream_id: "688edc60-a179-5618-90f1-468aadc2af58"
 ---
 
 Explicit NetKingdom target demand under CUST-WP-0080 selects the source evidence
@@ -25,6 +26,7 @@ service, portable signer, foreign owner review or live action is added.
 id: APPROVAL-WP-0004-T01
 status: done
 priority: high
+state_hub_task_id: "b0b0a5a9-f7e7-508b-96d0-4b02457b16fc"
 ```
 
 Source implementation supplies the HTTP-verified Identity to consume and writes
@@ -40,18 +42,40 @@ rollback. Source checks do not establish native acceptance.
 
 ```task
 id: APPROVAL-WP-0004-T02
-status: todo
+status: done
 priority: high
+state_hub_task_id: "2b932ef8-e143-5bb7-856e-4cba4fb22c09"
 ```
 
-The Custodian coordinator independently reviews the exact patch/manifest, then
-integrates and synchronizes the canonical owner record. Temporary-checkout work
-is not a canonical synchronized record or formal delegated-owner assent.
+The Custodian coordinator reviewed and integrated the exact source patch
+`a6bf77fa8b6916f423db7832f475e38747b828dd632a88f9631131e28e3230ee` as commit
+`477c683991fda3c01e2af98a18f5a8719ee9dbc9`. Canonical source hashes and integration
+are recorded in the-custodian's
+`docs/changes/netkingdom-target-2026-10-16/approval-reference/canonical-integration.json`.
+Normal State Hub sync/publication is recorded in the same change directory's
+`sync-session-61857.json`: bindings synchronized 5/5, source commit pushed, zero
+failures, zero automation errors and nine warnings. The generated-only writeback
+commit refusal remains recorded in that receipt; generated identifiers are
+retained. Published origin HEAD was independently read back as the exact commit
+above on 2026-10-16. This completes scoped source integration/publication, not
+formal delegated-owner assent or native acceptance. The closure-file update
+itself still follows the coordinator's normal review and synchronization.
 
 Existing native delivery obligations remain live under APPROVAL-WP-0002:
 T01 exact issuer/profile and release/migration, T04 admitted lifecycle source
 delivery/reconciliation, T05 named served PEP consumption before protected effect.
 Platform owns mediator transport/identity/custody, the one-shot journal and native
-effect; Secrets owns its actual strict handoff and task-scoped backend. Access
+effect; Secrets owns implementation of the strict handoff and task-scoped
+backend. The strict task handoff is not implemented at Secrets canonical
+`c80a944105a00220cd3c1a007709e72d830dd08d`
+and remains its next implementation work. Access
 owns the signed decision and exact request/action/representation binding. No
 claim that an isolated source test closes any of these gates is made.
+
+No scoped source work remains in APPROVAL-WP-0004. The native obligations above
+were live in APPROVAL-WP-0002 before this work and remain there under their
+existing identifiers and wait statuses; no new residual record is needed and
+no residual implementation is promoted by this closure. Further implementation
+of a necessary WP0002 residual must be explicitly selected under the continuing
+CUST-WP-0080 target demand and recorded with its precise owner/action scope;
+credential, rollout and native effect steps retain their separate authority gates.