Activate production Clock authority and verify host convergence

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a09cbb-87c6-7900-a145-4ce53ba9f1a6

workplans/RAIL-HO-WP-0013-host-time-baseline.md

@@ -9,7 +9,7 @@ flavor: planning
 owner: codex
 topic_slug: railiance
 created: "2026-09-14"
-updated: "2026-09-14"
+updated: "2026-09-15"
 related_workplans:
   - RCLK-WP-0005
   - RCLK-WP-0002
@@ -81,7 +81,7 @@ A mocked systemctl result or container-only check is not host synchronization pr
 
 ```task
 id: RAIL-HO-WP-0013-T04
-status: wait
+status: progress
 priority: high
 state_hub_task_id: "9adae3a6-8ee6-538b-9bb3-1ee32ed185e1"
 ```
@@ -99,3 +99,15 @@ railiance_clock owner role and host-time playbook; bootstrap invokes the same
 role. Authority activation requires artifact hash, admission reference and
 explicit signing-key delivery. Defaults change no clocks and deploy no service.
 Native convergence, custody and measured UTC policy acceptance remain open.
+
+## Live deployment — 2026-09-15
+
+CCR-2026-0028 authorizes the systemd authority and attended host-file custody.
+The role now prepares identity independently of key delivery, supports a verified
+preinstalled key, and pins the production wheel in Railiance01 inventory.
+The authority and health timer are active/enabled on loopback 8787. Readiness
+and signed workstation acceptance passed; receipt is in railiance-clock and
+railiance-platform docs/evidence/2026-09-15-railiance-clock-production.json.
+Health collection needs read-only adjtimex; ProtectClock is disabled only on
+that exporter, while both services retain empty capability sets. Disposable
+outage/reboot/rollback rehearsals remain tracked in T03.