Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a09cbb-87c6-7900-a145-4ce53ba9f1a6
60 lines
2.2 KiB
Markdown
60 lines
2.2 KiB
Markdown
---
|
||
id: RCLK-WP-0003
|
||
type: workplan
|
||
title: "Implement isolated authority and application clock"
|
||
domain: infotech
|
||
repo: railiance-clock
|
||
status: active
|
||
flavor: implementation
|
||
depends_on:
|
||
- RCLK-WP-0002
|
||
owner: codex
|
||
topic_slug: custodian
|
||
created: "2026-09-14"
|
||
updated: "2026-09-14"
|
||
depends_on_workplans:
|
||
- RCLK-WP-0002
|
||
state_hub_workstream_id: "904e08b5-978f-5bfc-b543-ca5347a56ac5"
|
||
---
|
||
|
||
Implement only the reviewed contract. Runtime language selection, API schema and dependency policy follow RCLK-WP-0002; no live secrets needed for fake-clock development.
|
||
|
||
## Implement authority sample and health adapter
|
||
|
||
```task
|
||
id: RCLK-WP-0003-T01
|
||
status: done
|
||
priority: high
|
||
state_hub_task_id: "0d7841ac-b652-54d5-8cb0-da430bf9ff9d"
|
||
```
|
||
|
||
Depends on 0002 adopted sample/trust/UTC contract. Implement bounded sample exchange, nonce binding, health/error state and epoch handling with disposable signing keys. Verify C02–C05/C13–C15.
|
||
|
||
## Implement application clock and attribution interface
|
||
|
||
```task
|
||
id: RCLK-WP-0003-T02
|
||
status: done
|
||
priority: high
|
||
state_hub_task_id: "b14d9306-eef8-5d78-8b3d-0c514cf10666"
|
||
```
|
||
|
||
Depends on adopted interval/platform contract. Provide explicit quality states, monotonic mapping, sample-age policy, restart/suspend invalidation and immutable event attribution. Verify C01/C06–C09/C11/C12.
|
||
|
||
## Prove isolated consumer integration and package review
|
||
|
||
```task
|
||
id: RCLK-WP-0003-T03
|
||
status: done
|
||
priority: high
|
||
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.
|