# railiance-clock

Authenticated application time for Railiance services and attached workstations
whose operating-system clocks are managed independently.

Status: Python reference implementation with a private host deployment recorded
on 2026-09-15. Contract review, native acceptance and consumer adoption remain
blocked on owner evidence; see the [closeout review](docs/closeout-review-2026-09-28.md).

Read [INTENT](INTENT.md), [scope](SCOPE.md), the [draft specification](specs/railiance-clock-v0.1.md),
[acceptance criteria](specs/acceptance-v0.1.md), and [ecosystem ownership](docs/ecosystem.md).

Workplan prefix: `RCLK-WP-`. Classification: tooling / infotech. Source is hosted
in the Coulomb Forgejo organization; repository registration does not admit a runtime.

## Workplans

- [0001 — Foundation and registration](workplans/RCLK-WP-0001-foundation.md)
- [0002 — Contract and trust review](workplans/RCLK-WP-0002-contract-review.md)
- [0003 — Reference implementation](workplans/RCLK-WP-0003-reference-implementation.md)
- [0004 — Deployment and consumer adoption](workplans/RCLK-WP-0004-deployment-adoption.md)

- [0005 — Infrastructure as code](workplans/RCLK-WP-0005-infrastructure-as-code.md)

Run the local reference suite with `uv run --extra dev pytest -q`. The CLI exposes
`read`, `serve`, and `health-export` (`uv run railiance-clock --help`).
`read --trust /path/to/trust.json` requires an independently admitted trust file;
a sample cannot admit its own key or renew trust. Deployment and credentials
remain with their existing owners.

[Registration and handoff evidence](docs/registration.md).

[Release verification](docs/release-verification.md) and
[acceptance coverage](docs/acceptance-coverage.md) describe repeatable package
checks and the limits of local test evidence.