Casework
Support for webhook delivery incidents should start with the event trail, the coverage window, and a human reviewer, not a confident guess.
“Did our webhook arrive?” is rarely a yes-or-no question.
A support engineer needs the event and endpoint IDs, delivery attempts, HTTP responses, retry schedule, and documentation before replying. A log export that ends before a scheduled retry cannot prove what happened after that point. A 2xx acknowledgment cannot prove the customer’s application completed its business action.
Correlate, ground, review, hand off.
The Python/SQLite reference backend ingests scoped delivery attempts and source-declared completeness windows. It derives a finding in code, snapshots the relevant evidence and runbook version, drafts a cited response, and blocks approval if new evidence makes the draft stale. Approval stages an idempotent outbox handoff to a separate demo support desk.
- Conflicting duplicate attempts are rejected; matching replays are harmless.
- Correlation includes customer, event, and endpoint identity.
- Overdue but unobserved retries are marked uncertain until source coverage supports a conclusion.
- A reviewer can edit, approve, or reject before handoff.
Use a model for language, not for deciding the facts.
The offline path uses templates. An optional model adapter can draft wording from selected evidence, a code-derived finding, and a versioned runbook. Structured output and citation checks constrain the draft; human review remains required. The hosted browser demo has no live AI model.
- ENGINE
- Python · SQLite · HTTP API
- INTERFACE
- React · TypeScript · monochrome operator workbench
- SAFETY
- Evidence freshness · citations · explicit review · transactional outbox
Try the incident. Inspect the contract.
In the demo, open ticket T-1042, advance export coverage, add a later HTTP 200, refresh the stale finding, then approve and hand off the revised answer. The hosted page saves synthetic state in the browser. The runnable Python backend is separate and is not connected to customer telemetry or a real support desk.
REFERENCE SYSTEM · SYNTHETIC INCIDENTS · NO PRODUCTION ACCURACY OR CUSTOMER IMPACT CLAIM