01
Components and sources
The approved status system should separately report public site, authentication, application, storefronts, APIs, file storage, email, integrations, and other material components using monitored evidence and operator confirmation.
02
Incident updates
A confirmed material incident should receive an initial notice, impact and affected components, investigation or mitigation updates, restoration notice, and a final resolution timestamp. Security details may be limited while risk remains.
03
History and post-incident review
Material incidents should remain available in an incident history. A post-incident review should identify timeline, impact, cause, correction, prevention work, and owners without exposing sensitive security information.
04
Technical indicators
Liveness and readiness endpoints support deployment monitoring but are not end-to-end transaction checks or contractual uptime measurements.
05
Report a problem
Record the time, workflow, workspace, visible error, and request identifier, then contact [email protected]. Never send passwords, tokens, private keys, or complete payment information.