Status pages
Status pages publishes the health of each Product and opens an Incident when a check fails, updating subscribers until it resolves.
Updates come from Monitoring as they happen, so no one writes them by hand.
Summary
| Part | This System |
|---|---|
| Group | Support |
| Status | Beta: it works, and its Verbs may still change |
| Shelf | Wakes: offered once its Event fires |
You can ask:
- “Put up a status page”
- “Tell customers the API is down”
- “Mark the incident resolved”
What you get
| Part | This System |
|---|---|
| Starts | On for every Startup at creation, with nothing to install. |
| Wakes | On Incident.opened. |
| Built from | Event streams, Workflows, Email delivery, Observability |
Nouns it owns
| Noun | Definition |
|---|---|
| Incident | An Incident is an Issue where an Interface or Site fails Customers in production, tracked from detection to postmortem. |
Verbs
| Verb | Object | Approval | Event |
|---|---|---|---|
| Incident.create | Incident | None | Incident.created |
| Incident.update | Incident | None | Incident.updated |
Events
| Direction | Event | How |
|---|---|---|
| Emits | Incident.created | By Incident.create |
| Emits | Incident.updated | By Incident.update |
States
None.
Who operates it
| Part | This System |
|---|---|
| Accountable | Operations Lead |
| Team | Operations Team |
| Seat | A role agent holds it until a Human is seated. |
| Autonomy | supervised |
| Also calls its Verbs | Privacy Officer |
Approvals and limits
None.
Processes that use it
| Process | How it uses it |
|---|---|
| Incident response | A Workflow writes Incident |
| Vulnerability disclosure | A Workflow writes Incident |
| Notify regulator | A step calls Incident.update |
Rail underneath
None.
Views and dashboards
| View | Shows | Metrics |
|---|---|---|
| The Operations Lead’s view | The Metrics its accountable Role answers for. | Liquidity |
Access
What each Access level may call here.
| Access level | May call |
|---|---|
owner | Every Verb (5) |
admin | Every Verb (5) |
member | Every Verb (5) |
viewer | Read only (2 of 5) |
Import and export
None.
Fees and pricing
None.
Availability and limits
| Part | This System |
|---|---|
| Status | Beta: it works, and its Verbs may still change |
Compliance notes
Controls it carries:
- Log completeness
- Append-only records
- Anomaly monitoring
- Incident handling
- Capacity headroom
- Action completion
Related Systems
Example
A Headless SaaS for verification codes sees delivery through one carrier slow to 40 seconds. Status pages opens an Incident on its status. subdomain and posts an update every 15 minutes. It emails the 300 subscribed developers when delivery recovers.