coulomb/railiance-clock
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Close clock scope review and record remaining owner blockers

Browse source 
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
Download patch file Download diff file Expand all files Collapse all files

11
SCOPE.md
View file

@ -1,10 +1,11 @@
# Scope
## Established in this seed
## Established
Founding intent, draft v0.1 specification, threat/acceptance model, owner boundaries,
registration procedure and staged workplans. This is a specification repository
baseline: no runtime, time endpoint, SDK, signing key or deployment is delivered.
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
@ -15,8 +16,8 @@ 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 remain RCLK-WP-0004 review
items. No high-availability, external timestamp notarization or production-security
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