From b987523e62da5475419a33e29426e4843d7d1af9 Mon Sep 17 00:00:00 2001 From: tegwick Date: Thu, 24 Sep 2026 15:43:55 +0200 Subject: [PATCH] Finish the isolated clock reference implementation. Assistant: grok Assistant-Session: 01a0d25d-d358-7e13-b84a-d007fbb7e34f --- .../RCLK-WP-0003-reference-implementation.md | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/workplans/RCLK-WP-0003-reference-implementation.md b/workplans/RCLK-WP-0003-reference-implementation.md index f9a5811..4b2151d 100644 --- a/workplans/RCLK-WP-0003-reference-implementation.md +++ b/workplans/RCLK-WP-0003-reference-implementation.md @@ -4,14 +4,14 @@ type: workplan title: "Implement isolated authority and application clock" domain: infotech repo: railiance-clock -status: active +status: finished flavor: implementation depends_on: - RCLK-WP-0002 owner: codex topic_slug: custodian created: "2026-09-14" -updated: "2026-09-14" +updated: "2026-09-24" depends_on_workplans: - RCLK-WP-0002 state_hub_workstream_id: "904e08b5-978f-5bfc-b543-ca5347a56ac5" @@ -53,8 +53,13 @@ state_hub_task_id: "7aa67eff-af5b-5a99-97bf-1bdee81acde1" Run deterministic boundary/property tests plus adversarial delay/replay and real platform lifecycle probes. Demonstrate +/− local clock skew with no OS changes. Preserve consumer approval/CAS failures with fixtures; publish dependency/SBOM and reproducible build evidence. No native production claim from synthetic fixtures. -Implementation started 2026-09-15 under the operator request to implement the -time infrastructure and its consumers. Source now contains the isolated JWS -authority/client, conservative interval checks, Linux lifecycle detection and -host health export. Twenty initial client/security tests pass. This is not yet -native service admission, measured timer acceptance, or completed deployment. +Closed 2026-09-24 on the reference-implementation boundary. The three tasks +deliver the isolated authority sample, the application clock, and consumer +integration under synthetic fixtures. No native production claim is made from +those fixtures. + +Native admission, measured timer acceptance, and deployment are already live +records and are not leftovers of this plan. `RCLK-WP-0005` owns +infrastructure-as-code delivery. `RCLK-WP-0004` owns the railiance01 pilot and +the first consumer migration, and it waits on `RCLK-WP-0005` as well as this +plan.