Every confirmed operational incident on bridger.levenhall.com — what happened, when, who was affected, what we did, and what we changed afterward. We commit to publishing within 5 business days of resolution.
If a single user encountered a 500 error twice, that goes in the log. If our cron missed a day, that goes in the log. We’d rather over-report than under-report — the silent failures are the dangerous ones.
SEV1: platform-wide outage or data exposure. Notification within 1 hour to all account holders.
SEV2: partial outage affecting a single tier or region. Notification within 24 hours.
SEV3: degraded feature or single-cron failure. Logged here within 5 business days.
SEV4: minor bug or near-miss. Logged here at month-end.
The platform has operated without a customer-facing outage since the public launch window. The detailed SEV3/SEV4 log will populate here as we accumulate operational history. We do not delete past entries.
Email the operator at hgad@levenhall.com with subject “[Incident]” and as much detail as you can: timestamp, account ID, browser, repro steps. We respond within 4 business hours.
Use the responsible disclosure path documented in /.well-known/security.txt. We acknowledge within 48 hours and target initial triage within 5 business days.