Skip to main content

Crate polyc_runtime

Crate polyc_runtime 

Source
Expand description

Shared Unix-coherence scaffolding for polychrome binaries (PRD §11): structured logging, a health/metrics side-server, and signal-driven graceful shutdown. Used by both the control plane and the harness so the two binaries behave identically under Kubernetes.

Modules§

admission
Shared admission control for edge webhook handlers (#795).
compat
Update compatibility classifier — the safety interlock at the heart of the update model.
ghcr
Shared OCI-registry helpers: the published-component roster plus immutable manifest-digest resolution, registry-agnostic.
health
The axum side-server (PRD §11): liveness, readiness, and metrics on a separate port from a binary’s main surface.
hot_reload
Hot config-as-data reload — apply a verified bundle at the turn boundary, with no process restart (see the update PRD and crate::compat / crate::stager).
observability
Logging + traces + panic discipline (PRD §11).
propagation
W3C traceparent propagation across the connectrpc boundary.
release_manifest
The release digest manifest (release-images.yaml).
retry
Rate-limit-aware retry for edge platform REST clients (#795).
signals
Signal-driven graceful shutdown (PRD §11).
stager
Update stager — the apply substrate the hot and warm update paths build on.
supervise
Server-task supervision: run a binary’s spawned servers until a shutdown signal, treating any earlier exit as fatal.
update_copy
The one place an available update is worded for a person.