SEV-1
Money or data
Immediate halt of new liability, incident channel, customer notice.
Status· design stage
Know which parts are real yet.
This page describes the design-stage posture. It is not a live incident feed and it does not report uptime for services that are not generally available.
01 / COMPONENTS
Component posture.
“Sandbox” means usable against fixtures. “Target” means specified but not certified. “Prototype” means code exists with known gaps.
| Component | State | Note |
|---|---|---|
| Public site | LIVE | Static, no third-party requests |
| Sandbox API | SANDBOX | Fixture data; no media purchased |
| Cockpit | PROTOTYPE | Local tests; not generally available |
| Rust bidding edge | PROTOTYPE | Local test harness only |
| MCP control plane | PROTOTYPE | Older handshake revision |
| Production providers | TARGET | No live partner credentials claimed |
| Billing rail | TARGET | Simulated only |
02 / INCIDENTS
How incidents will be handled.
During general availability, incidents are classified by financial and privacy impact. Status updates are posted here and to subscribers; emergency stops are described in the security model.
SEV-2
Delivery
Continue from last-good state; publish scope and workaround.
SEV-3
Degraded UI
Queue durable work; no silent retry of financial actions.