Status Scope
Signals a real status page must separate
Provide transparent status-page structure without publishing invented operational state, uptime percentages, incident counts, or automated-monitoring claims.
Status Scope
Signals a real status page must separate
- 01 Public status criteria Published only for HRHK-hosted or HRHK-managed services with external users
- 02 Client-facing service scope Requires a real monitoring source, owner, and update process
- 03 Approved monitoring source Uses dated, scoped updates when an event affects an externally consumed service
- 04 Maintenance notices Shown only when retained monitoring data supports the claim
- 05 Incident communication Published only for HRHK-hosted or HRHK-managed services with external users
- 06 Historical uptime only when evidenced Requires a real monitoring source, owner, and update process