# Scope

## Established

Founding intent, draft v0.1 specification, threat/acceptance model, owner boundaries,
registration and a Python reference authority/client with local tests. A private
systemd deployment on railiance01 was recorded on 2026-09-15. That historical
receipt does not close native recovery, measured policy or consumer adoption gates.

## Planned v0.1

One monitored UTC authority on railiance01; authenticated fresh sample exchange;
process-local monotonic clock with uncertainty and explicit unusable states;
append-only timestamp attribution; one explicitly reviewed consumer pilot.

## Deferred live work

Distributed authority consensus, active/active failover, public NTP/NTS service,
long offline holdover and additional language clients are deferred beyond v0.1
by the completed RCLK-WP-0004-T04 [scope review](docs/closeout-review-2026-09-28.md). No high-availability, external timestamp notarization or production-security
adoption claim is made by the single-host pilot.

## Authority boundary

The local specification proposes a contract. RCLK-WP-0002 owns cross-repository
review before its security use. RCLK-WP-0003 owns reference implementation and
RCLK-WP-0004 owns admitted deployment and consumer evidence. Statehub indexes
source records; it is not a time source. Forgejo hosts records, not a UTC oracle.

RCLK-WP-0005 explicitly owns IaC setup, host discipline, authority packaging,
bootstrap sequencing, native deployment and operational handoff. Bootstrap calls
owner automation; ongoing configuration remains in S1 and workload owners.