reference
SupportOS SLO and incident authority
Privacy-safe SLO evidence, incident lifecycle, paging, and review contracts.
Public inputs never carry tenant, workspace, actor, timestamps, computed verdicts, or receipt authority. SLO evidence separates API and customer-surface availability windows and binds a stable source digest to opaque telemetry, incident, and drill references. Incident mutations are revision-fenced and idempotent; lifecycle actions contain only typed taxonomy and opaque references, never narrative, customer content, destinations, or provider payloads. Lists use bounded keyset cursors and a stable server watermark. Fixture evidence proves deterministic behavior but never qualifies production SLO, alert delivery, paging coverage, drills, or canaries.