Review the investigation.
Keep the evidence.
A safe, read-only replay of Incident Desk. Every service, person and observation below is invented. Opening this page sends no notification, starts no agent and changes no application.
Situation report
The visitor-book page is unavailable in this fictional example; a shallow health check still responds.
- Service / owner
- Fictional Trail Notes · Fictional Team A
- First / last seen
- 2026-10-25T00:00:00Z / 2026-10-25T00:03:00Z
- Reported recovery
- Unverified — incident remains open
- Owner notice
- Not sent
- PagerDuty
- Not connected
Observed
- The visitor-book journey returns 500; the health route returns 200. Evidence: journey-01
- The separate Team B control still returns its expected content. Evidence: control-01
Hypotheses to test
- possible: The optional caption is used as text before its presence is checked.
Next check: Run the exact request with a missing caption and compare the retained source.
- possible: The data service may be unreachable.
Next check: Check the scoped data read independently; do not infer health from a root response.
Steps already taken
- Retained the failing request and the unchanged control result.
- Prepared an investigation proposal; no recovery action has run.
Unknowns and blockers
- Root cause and compatible recovery remain unverified.
- No email or PagerDuty connection has been exercised.
Next update: After the missing-caption reproduction and scoped data check are attached to a new proposal version.
The owner sends it back
“Keep the failing request and the control result. Test a missing caption, check the data read, and show a regression check before asking for approval.”
- Version 1 · investigation proposed.
The exact source, scope, observations, competing hypotheses and proposed work receive one digest.
- Send back · instructions retained.
The first investigation remains readable. Its review reason stays attached to version 1; the previous digest cannot approve a revised plan.
- Version 2 · evidence added.
A local agent submits its checks through the existing scoped connection. The owner compares both versions and decides on the new digest.
- Approve or reject · work preserved.
Approval records the proposal decision. A separate authorised handoff must check the current target and source before execution. Rejection closes that proposal and keeps its evidence.
The private page uses the existing proposal store, workspace roles, source checks and review endpoints. A viewer cannot decide; an agent cannot approve itself; stale versions and revoked grants are refused.
What remains a separate check
Real failure detection, authorised recovery, configured owner email and PagerDuty each need their own recorded proof. This replay establishes none of those. The local availability lab already exercises a separate visibility failure and recovery; it is not a production responder.