Close clock scope review and record remaining owner blockers

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e6f0-a6f6-7b93-9124-55ef584930e2

README.md

@@ -3,7 +3,9 @@
 Authenticated application time for Railiance services and attached workstations
 whose operating-system clocks are managed independently.
 
-Status: specification and planning baseline; no service is deployed.
+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).
@@ -20,7 +22,10 @@ in the Coulomb Forgejo organization; repository registration does not admit a ru
 
 - [0005 — Infrastructure as code](workplans/RCLK-WP-0005-infrastructure-as-code.md)
 
-No installation is required to review these documents. Runtime commands and
-examples will be added only with their implementation and verification.
+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).