Overview
Public Status Page
Publish a public page of your components and their current status, keep visitors informed through incidents and scheduled maintenance, and email confirmed subscribers every update an operator posts.
Pull this Blueprint
One command, no account. It expands into a canonical product-model/ directory without touching repository-owned files.
npx @itai-gendler/pdd-kit@latest blueprint pull public-status-page Then hand the directory to a coding agent, or refine the Product Model with pdd-ideate first.
Description
A public page where an operator team tells the people who depend on its service what is working right now. Operators list the components of their service and set each one's status, declare incidents and post updates on a timeline until they are resolved, and schedule maintenance ahead of time. Visitors read the page without an account and can subscribe by email to hear about every update. During an incident an operator can ask for a draft: from the operator's rough notes, the Product fills in the text of the next update with a language model.
Intent
When a service breaks, the people who depend on it cannot tell whether the problem is theirs, and the operators who could tell them are busy fixing it. The page gives them one honest, timely place to learn what is wrong, what is being done, and when it is over — and spares the operators the writing.
Limitations
Deliberate exclusions or constraints of the Product.
Component status is what an Operator sets; the Product does not monitor components or measure uptime itself.
Subscribers are notified by email only.
The Product keeps one status page for one operator team, and anyone can read it; there are no private or audience-restricted pages.
Components are one flat list; they are not grouped or nested.
Incidents, their updates and maintenance windows are never deleted, and a posted update is never edited; a correction is a later update.
A maintenance window's times and components are never edited; a changed plan is a cancelled window and a new one.
A language model drafts an update's message from the Operator's notes and can get it wrong; the Operator edits it and decides whether to post it. While the language model is unavailable, Operators write every update themselves.
Operators sign in with an existing account, and who belongs to the operator team is managed outside the product; Visitors read the page without one.
Source
- Path
- blueprints/public-status-page
- Commit
- f474777f1700
- Report digest
- 16aff525023667c3…
Blueprints are curated in itai-gendler/pdd-kit. Propose one with pdd-kit blueprint contribute.