Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0e6f0-a6f6-7b93-9124-55ef584930e2
78 lines
3 KiB
Markdown
78 lines
3 KiB
Markdown
---
|
||
id: RCLK-WP-0003
|
||
type: workplan
|
||
title: "Implement isolated authority and application clock"
|
||
domain: infotech
|
||
repo: railiance-clock
|
||
status: finished
|
||
flavor: implementation
|
||
depends_on:
|
||
- RCLK-WP-0002
|
||
owner: codex
|
||
topic_slug: custodian
|
||
created: "2026-09-14"
|
||
updated: "2026-09-28"
|
||
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.
|
||
|
||
|
||
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.
|
||
|
||
|
||
### Release-evidence follow-up — 2026-09-28
|
||
|
||
T03 now has a repeatable [release verifier](../docs/release-verification.md),
|
||
hash-pinned build tools, independent byte-identical wheel/sdist build evidence,
|
||
an isolated installed-wheel signed HTTP/CLI smoke check, and a runtime SBOM.
|
||
The [acceptance coverage map](../docs/acceptance-coverage.md) explicitly records
|
||
that the original task prose exceeds current evidence: no local approval/CAS
|
||
concurrency fixture or historical event-translation test, and no complete native
|
||
platform or consumer proof. Finished status retains only the previously stated
|
||
reference boundary; those broader claims are not asserted. Existing
|
||
0002-T04/0004-T02/T03 and 0005 retain their owner/native gates.
|