State Taxonomy Matrix
Never say state vaguely. Classify owner, writer, durability, recovery, deploy impact, scale impact, and failure behavior.
Selected tab/form draft
Vango session
Writer
Session loop
Durability
ephemeral unless explicitly persisted
RPO
0 to fresh-session acceptable
Deploy impact
warm if schema compatible; cold if removed/unknown
Scale impact
pinned to allocation unless durable resume exists
Failure behavior
lost on process death unless persisted
Persisted Vango session state
Vango app with Rhone session store
Writer
Session loop through state API
Durability
durable runtime service
RPO
plan-specific, usually low
Deploy impact
state schema impact controls warm/cold
Scale impact
can hydrate on another allocation if compatible
Failure behavior
hydrate or fresh-session with clear UX
Product data
Application database
Writer
App Actions/workers
Durability
database durability/PITR
RPO
customer plan dependent
Deploy impact
migration impact controls deploy/rollback
Scale impact
shared by allocations through DB
Failure behavior
restore/repair according to DB RPO/RTO
Route ownership
Rhone control plane
Writer
Promotion/rollback operation
Durability
control database plus edge snapshots
RPO
near-zero for production
Deploy impact
changes only through artifact/deploy policy
Scale impact
edge consumes monotonically by epoch
Failure behavior
fail closed or rebuild snapshot on replay gap
Allocation health
Regional data plane
Writer
Runner/scheduler
Durability
runtime database
RPO
seconds/minutes acceptable
Deploy impact
new deploy creates replacement allocations
Scale impact
affects target selection, not route authority
Failure behavior
scheduler replaces; sessions drain or fail
Operation state
Rhone control plane
Writer
API/worker stages
Durability
control database
RPO
near-zero for mutations
Deploy impact
records promotion/deploy/migration evidence
Scale impact
all clients read same mutation truth
Failure behavior
resume/reconcile from durable stage records
Build logs
Pipeline/log store
Writer
Builder
Durability
log/object store
RPO
minutes acceptable
Deploy impact
diagnostic only
Scale impact
not used for correctness
Failure behavior
may be partial; operation state remains truth
Provider credentials
Rhone secret store
Writer
Provider binding operation
Durability
encrypted secret backend
RPO
near-zero for active prod
Deploy impact
rotation may require allocation restart
Scale impact
region-scoped availability gates placement
Failure behavior
disable binding or rotate; never leak to logs
NATS route events
Event bus
Writer
Control-plane publisher
Durability
JetStream retention
RPO
bounded replay window
Deploy impact
propagates route changes
Scale impact
lets edges converge without polling every request
Failure behavior
dedupe/stale/replay-gap handling required