CUST-WP-0075 owner-return sweep: RCLK-WP-0002-T01 done, all three returns recorded

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 3775@bnt-lap001
Assistant-Session: cfacb6a5-ad5b-4f79-ac67-053e3b0d34a3

workplans/RCLK-WP-0002-contract-review.md

@@ -11,7 +11,7 @@ depends_on:
 owner: codex
 topic_slug: custodian
 created: "2026-09-14"
-updated: "2026-09-28"
+updated: "2026-10-03"
 depends_on_workplans:
   - RCLK-WP-0001
 state_hub_workstream_id: "8a320731-32a6-5d33-9517-2242a05c0d30"
@@ -23,9 +23,7 @@ Ready to perform review of the completed draft, not ready for production securit
 
 ```task
 id: RCLK-WP-0002-T01
-status: wait
-blocked_on: message-from:gate-house
-blocking_reason: "Gate-house review, registry/custodian prefix confirmation and architecture disposition of rapp coverage versus host-service delivery."
+status: done
 priority: high
 state_hub_task_id: "437734bd-8930-56d5-9eb3-2835cb19db8b"
 ```
@@ -34,6 +32,24 @@ Blocked as of 2026-09-28: gate-house review, registry/custodian prefix confirmat
 
 Obtain Railiance architecture and NetKingdom/gate-house review. Resolve authority host operation, Forgejo evidence role, source/runtime packaging and time-provider layer/PEP classification. Publish adopted role declaration only after review. Confirm RCLK-WP prefix ownership.
 
+2026-10-03 (CUST-WP-0075 owner-return sweep): all three parts of the gate are
+returned, so T01 is done.
+- Architecture disposition: railiance-master replied 2026-09-21 (message
+  `2596094f`, read 2026-09-28, not recorded here until now). The application
+  time service is a workload under the rapp coverage rule (ADR-0007): its own
+  rapp declaration owned by railiance-clock, on rail-kubernetes, bound to
+  reef-railiance on railiance01 via ADR-0006 admission; private placement is
+  required (ADR-0008). S1 host UTC belongs to railiance-infra (ADR-0004).
+- Gate-house review: replies `f1d7ba98`, `7071237a`, `817f0672` and summary
+  `2b1cf24d` (2026-10-03). `layer: Tooling` conforms; findings: runtime_identity
+  must be the concrete workload instance (net-kingdom/audit-core), the trust
+  owner for key binding and revocation is unnamed, and protected consumers must
+  refuse rather than fall back to the local clock (T04/C16 contract).
+- Prefix: repo-manager registered `RCLK-WP: railiance-clock` (`03869ff`,
+  reply `f339445a`).
+Follow-on work these rulings create (rapp declaration, reef admission, trust
+owner) belongs to T02-T04 and RCLK-WP-0004/0005, not to this gate.
+
 ## Specify authenticated samples and trust lifecycle
 
 ```task