Incidents and status
Understand how ZYNC should communicate service disruption, security events, affected promises, and recovery.
An incident is an event that threatens availability, confidentiality, integrity, safety, or a material product promise.
Public status communication should state:
- which service or flow is affected;
- when the issue began and was detected;
- the impact users may observe;
- whether actions should be paused;
- containment and recovery progress;
- the time of the next update;
- final resolution and follow-up.
Do not report an internal system as healthy when the Member outcome is failing. A page can load while verification, reward release, or cashout is impaired.
Security details may need temporary limits during containment, but the final report should explain the affected boundary, material impact, correction, and prevention work.
ZYNC’s observability design includes technical signals, business invariants, reconciliation, and traceability. A production status page and contact route must be verified before this documentation can be marked Available.