API
Monitor-readySaaS API boundary and public health response.
- Initial source
- GET /api/v1/health
- Current handoff
- Ready for provider polling
Customer-safe status
Public status contract, ready for provider handoff.
The live provider-backed status page is still a separate A11 setup task. This route now mirrors the public component model and keeps private diagnostics out of customer-facing copy.
Web app
Manual until public signalCustomer web frontend.
- Initial source
- Frontend uptime monitor after deployment
- Current handoff
- Manual until deployment monitor exists
Telegram delivery
Manual until public signalTelegram message delivery path.
- Initial source
- Bounded delivery success signal
- Current handoff
- Manual until delivery signal exists
Discord delivery
Manual until public signalDiscord message delivery path.
- Initial source
- Bounded delivery success signal
- Current handoff
- Manual until delivery signal exists
FPL data sync
Manual until public signalFPL API ingestion and scheduler freshness.
- Initial source
- Public-safe freshness signal
- Current handoff
- Manual until freshness signal exists
Signup
Manual until public signalSignup, auth, checkout, and onboarding path.
- Initial source
- Signup and checkout readiness signal
- Current handoff
- Manual until launch signal exists
Incident copy boundary
Public updates describe impact, not internals.
Use customer-impact language only; private diagnostics stay out of public status content.
- Publish customer-visible impact, current state, and next update time.
- Keep internal diagnostics in operator runbooks, not public status copy.
- Fail closed to manual status until a bounded public signal exists.