Expand description
In-daemon at9p service-identity renewal timer (design O-Ia).
The registry daemon is the deployment’s sole read-write record-store
owner, so it hosts one periodic task that renews every DEPLOYMENT service
identity itself (O-Ia) — the accepted states whose #service entries
name daemon services (hyprstream_service::get_factory), not generic
at9p records admitted through the public RPC — reusing the boot
provisioner’s mint core
([crate::cli::deployment_bootstrap::provision_one]) against the daemon’s
LIVE PdsRecordStore/At9pStateIngest handles. It must never call
provision_services as-is — that re-opens the store (self-conflicting on
the RocksDB directory LOCK the daemon already holds) and re-runs
authenticate_local_deployment_registry per invocation, which would drag
the ≤1 h credential / 30 d delegation dependency back into every tick.
The deployment credential/UCAN is checked exactly once per process start;
admission itself needs only the pre-committed on-volume chain keys and the
daemon clock, so a running process renews for its lifetime while restarts
still gate on the credential (unchanged by this timer).
Trust property (review note): signing sibling services’ successors
routinely from the long-lived registry process differs in process context
— not in authority — from the offline exclusive-window mint. The signing
material is identical (each service’s on-volume key, pre-committed in
next_key_commitments), and every admission invariant still holds:
key mismatch refuses (never substitutes), terminal identity refuses, the
same key carries forward, successors are epoch+1, expiry is evaluated
on the daemon’s clock with no skew tolerance, and the commit is the same
guarded CAS as the RPC path.
Every tick also re-exports the roster projection
(<data>/config/native-network/roster.json by default) through the same
readback-verified atomic writer as the boot command, so host-side
monitoring that flags a roster whose generated_at ages past a day reads
fresh expiries — and a stale roster means this loop died, not that
nothing was due. The boot-time roster.candidate.json → config.toml
native-config projection stays boot-scoped host tooling: runtime consumers
(native announcements) re-project from the store, never from that file.
The same writer tick refreshes an idle PDS model-record head from its authenticated sealed ES256 generation. This is independent of at9p chain renewal and preserves the record pointer/unsigned commit; the two attempts cannot starve each other on an unrelated failure.