Close clock scope review and record remaining owner blockers

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e6f0-a6f6-7b93-9124-55ef584930e2
This commit is contained in:
tegwick 2026-09-28 09:39:50 +02:00
parent 61e86a6e01
commit a6db15d202
10 changed files with 179 additions and 43 deletions

View file

@ -4,14 +4,14 @@ type: workplan
title: "Review time authority, trust and consumer contracts"
domain: infotech
repo: railiance-clock
status: active
status: blocked
flavor: planning
depends_on:
- RCLK-WP-0001
owner: codex
topic_slug: custodian
created: "2026-09-14"
updated: "2026-09-14"
updated: "2026-09-28"
depends_on_workplans:
- RCLK-WP-0001
state_hub_workstream_id: "8a320731-32a6-5d33-9517-2242a05c0d30"
@ -23,44 +23,52 @@ Ready to perform review of the completed draft, not ready for production securit
```task
id: RCLK-WP-0002-T01
status: progress
status: wait
priority: high
state_hub_task_id: "437734bd-8930-56d5-9eb3-2835cb19db8b"
```
Blocked as of 2026-09-28: gate-house review, registry/custodian prefix confirmation, and architecture disposition of rapp coverage versus host-service delivery.
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.
## Specify authenticated samples and trust lifecycle
```task
id: RCLK-WP-0002-T02
status: progress
status: wait
priority: high
state_hub_task_id: "5f7dd460-06d7-59ef-9d37-102ca9a22f6c"
```
Blocked as of 2026-09-28: Infrastructure/platform/trust owners accept source/leap, custody refresh/revocation and epoch/rollback recovery contract; NK-WP-0040 remains the execution-receipt dependency.
Choose established signing profile, canonical encoding and wire schema; trust bootstrap, key distribution/rotation/revocation, replay/nonce scope, authority epoch and rollback recovery. Pin upstream UTC/leap convention and defend delayed authentic samples. Satisfy C02–C05/C09/C14.
## Specify measured clock bounds and platform lifecycle
```task
id: RCLK-WP-0002-T03
status: progress
status: wait
priority: high
state_hub_task_id: "8038f9ee-8585-57e3-a769-701e16ff7e8b"
```
Blocked as of 2026-09-28: Infrastructure and supported-platform owners accept measured timer/error/suspend assumptions; no universal VM drift bound inferred.
Review interval arithmetic with explicit timer/upstream assumptions, drift/age policies and unsupported-platform behavior. Define Windows/Linux/WSL suspend/reboot detection and telemetry. No guessed ppm or offline lifetime as proven policy. Satisfy C01/C06/C08/C13/C15.
## Adopt consumer and audit time semantics
```task
id: RCLK-WP-0002-T04
status: todo
status: wait
priority: high
state_hub_task_id: "53d248c0-b73d-5ee7-a3a8-360bd1b1042d"
```
Blocked as of 2026-09-28: access-engine (runtime flex-auth), approval-engine, secrets-engine and audit-core return accepted contract versions and native boundary/CAS evidence.
Agree with flex-auth, approval-engine, secrets-engine and audit-core on clock injection/server-side execution, validity boundaries, CAS/check-to-use semantics and event attribution. Preserve current refusal until reviewed replacement. Pin accepted contract versions and update acceptance matrix C07/C10–C12/C16. Record disagreements as decisions/live work.
Review started 2026-09-14: `docs/identity-and-utc-review.md` pins the IAM/layer
@ -74,3 +82,10 @@ and twenty structural negatives; no crypto/lifecycle/UTC acceptance claimed.
Trust delivery, measured timer/error policy, leap and rollback recovery remain
owner review gates. Custodian response 03014307-20b6-47d3-81f4-7f12fcaed014
confirms discovery only and does not close admission tasks.
### Closeout review — 2026-09-28
Remaining tasks wait on owner review or native evidence; this plan is blocked.
The [closeout review](../docs/closeout-review-2026-09-28.md) records the completed
portions, each remaining gate and its owner. No new task or workplan was opened.

View file

@ -4,7 +4,7 @@ type: workplan
title: "Admit railiance01 pilot and migrate one consumer"
domain: infotech
repo: railiance-clock
status: proposed
status: blocked
flavor: implementation
depends_on:
- RCLK-WP-0003
@ -12,7 +12,7 @@ depends_on:
owner: codex
topic_slug: custodian
created: "2026-09-14"
updated: "2026-09-14"
updated: "2026-09-28"
depends_on_workplans:
- RCLK-WP-0003
- RCLK-WP-0005
@ -30,6 +30,8 @@ priority: high
state_hub_task_id: "a4040b78-ba86-54aa-b6b5-43fdefb3ddda"
```
Blocked as of 2026-09-28: 0005 completes placement/custody/health delivery and 0002 contract acceptance; rail/reef or reviewed host-exception coverage.
Consume RCLK-WP-0005 infrastructure placement, custody, health and exact-source deployment receipts. Verify they satisfy the adopted 0002/0003 contract before consumer pilot. Infrastructure implementation belongs to 0005 and its owner records, not a duplicate apply here.
## Measure and verify the native authority/client pilot
@ -41,6 +43,8 @@ priority: high
state_hub_task_id: "28b4c1e0-833c-583d-9cca-fd794d58a0ac"
```
Blocked as of 2026-09-28: Admitted native test targets and 0005 prerequisites; measured skew/suspend/outage/recovery coverage with accepted thresholds.
Exercise skewed corporate workstation without OS changes, bootstrap limitations, source outage, restart/rollback, delayed samples and suspend/resume. Measure interval coverage/width, latency and holdover; agree versioned thresholds. Verify cleanup, rollback and authority-key revocation. Retain audit evidence, not secrets.
## Migrate one explicitly admitted security consumer
@ -52,15 +56,24 @@ priority: high
state_hub_task_id: "2d7b4769-0196-5108-83a4-4b481f20d923"
```
Blocked as of 2026-09-28: Named consumer owner's admission and native identity, expiry, uncertainty and concurrent-consume negatives.
Choose server-side native execution where feasible. With consumer-owner approval, test correct use and wrong-caller/owner/tenant/signature/expiry negatives, uncertain boundaries and concurrent consume. Update the consumer contract before replacing its clock. IR-WP-0004/SECRETS-WP-0010 remain independently open until their own return gates pass.
## Review operational scope and hand off later capabilities
```task
id: RCLK-WP-0004-T04
status: wait
status: done
priority: high
state_hub_task_id: "dc91e30a-412d-5406-8921-25ce4773c785"
```
Review availability/SLO, independent backup authorities, long offline holdover, additional languages and optional authenticated NTP/NTS infrastructure offering. Keep single-host limitations explicit. Any actionable work not delivered becomes live successor records before this plan finishes.
### Closeout review — 2026-09-28
T04 is complete: single-host scope and deferred capabilities are decided. Remaining tasks wait on owner review or native evidence; this plan is blocked.
The [closeout review](../docs/closeout-review-2026-09-28.md) records the completed
portions, each remaining gate and its owner. No new task or workplan was opened.

View file

@ -4,12 +4,12 @@ type: workplan
title: "Deploy clock infrastructure through owner-managed infrastructure as code"
domain: infotech
repo: railiance-clock
status: active
status: blocked
flavor: implementation
owner: codex
topic_slug: custodian
created: "2026-09-14"
updated: "2026-09-15"
updated: "2026-09-28"
related_workplans:
- RCLK-WP-0002
- RCLK-WP-0003
@ -53,11 +53,13 @@ declares it in IaC after RCLK-WP-0002.
```task
id: RCLK-WP-0005-T02
status: progress
status: wait
priority: high
state_hub_task_id: "f3eea5a7-e745-57a2-9d76-b78eeba0bf06"
```
Blocked as of 2026-09-28: RAIL-HO-WP-0013 policy acceptance, baseline health integration and disposable reboot/outage/convergence evidence.
Depends on T01 and RCLK-WP-0002's UTC/leap/quality contract. In the S1 owner,
version the selected existing/supported NTP client, independent upstream selection,
network requirements, boot/restart behavior, holdover limits, drift monitoring and
@ -75,11 +77,13 @@ alone does not prove bounded UTC accuracy.
```task
id: RCLK-WP-0005-T03
status: progress
status: wait
priority: high
state_hub_task_id: "bc07711b-96d1-5d72-aee1-21d39942564c"
```
Blocked as of 2026-09-28: Final architecture coverage and platform-approved durable trust refresh/rotation with native evidence.
Depends on adopted RCLK-WP-0002 trust contract and RCLK-WP-0003 artifact. Use
rail-kubernetes on reef-railiance as the initial packaging candidate; create the
reviewed rapp/deployable declarations under the architecture owner's conventions.
@ -107,6 +111,8 @@ priority: high
state_hub_task_id: "584440e4-49ce-57f4-b6f1-953c0feec710"
```
Blocked as of 2026-09-28: Bootstrap owner fresh-estate and upgrade rehearsal, failed-time gate and steady-state handoff receipts.
Coordinate with railiance-bootstrap after T01 establishes owners. Add ordering:
S1 obtains usable external UTC and basic transport trust; S2/S3 bring up the
required substrate and admitted custody; the authority service is deployed;
@ -123,11 +129,13 @@ state owners. No unsupported claim that corporate workstations can be converged.
```task
id: RCLK-WP-0005-T05
status: progress
status: wait
priority: high
state_hub_task_id: "1b9fa2cb-77c5-5519-a4d3-184cb8597f86"
```
Blocked as of 2026-09-28: Admitted disposable VM recovery/drift/rebuild/rollback proof, then specifically authorized native verification through S1 owner.
Depends on T02/T03 readiness and specific live owner authorization. Apply the
reviewed source revision through its normal owner pipeline. Keep clock steps
and effects on existing token consumers within the reviewed rollout window.
@ -150,6 +158,8 @@ priority: high
state_hub_task_id: "c2edb898-7446-5e82-8d2a-9f3f45f41b00"
```
Blocked as of 2026-09-28: Telemetry/platform accept alerts, budgets, recovery/rotation runbooks and native evidence from preceding tasks.
Deliver alert ownership, quality/error budgets, backup/recovery and key-rotation
runbooks, source locations, pipeline/placement identifiers and native evidence to
railiance-telemetry/platform and RCLK-WP-0004. Document what remains single-host.
@ -157,7 +167,7 @@ Keep all unresolved work as live records before finishing this plan. RCLK-WP-000
may adopt a protected consumer only after this infrastructure gate AND its own
explicit consumer review/negative tests pass. A deployed endpoint is not a grant.
## Production deployment evidence — 2026-09-15
### Production deployment evidence — 2026-09-15
The operator approved CCR-2026-0028 for platform and Clock ownership and then
accepted systemd host delivery. Authority and health timer are active/enabled
@ -176,7 +186,14 @@ Readiness and three workstation signed samples passed, with interval widths
interval construction against the same host, not independent UTC consensus.
Evidence: docs/evidence/2026-09-15-railiance-clock-production.json.
T02/T03/T05 remain in progress for the broader acceptance criteria: disposable
At deployment, T02/T03/T05 remained in progress for the broader acceptance criteria: disposable
reboot/outage/rotation/rollback rehearsals, durable consumer trust refresh, and
operational handoff in T06. Per-run consumer admission is boot-bound and expires
after 15 minutes; this deployment does not enable every optional consumer.
### Closeout review — 2026-09-28
Remaining tasks wait on owner review or native evidence; this plan is blocked.
The [closeout review](../docs/closeout-review-2026-09-28.md) records the completed
portions, each remaining gate and its owner. No new task or workplan was opened.