Cancel obsolete drafts when new incident context arrives
An older slow response overwrites the summary after a recovery event arrives.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Concurrency · Provider design
Estimated field mix
- Applied AI60%
- Backend40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional on-call team wants an assistant that joins alerts, deployment notes, and runbooks. Incomplete telemetry and hostile log content make unsupported conclusions dangerous.
Setup prerequisites
- Author synthetic alerts, deployment records, and runbooks plus deterministic tool and model doubles.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Bind drafts to context revision.
- Cancel or discard superseded work.
- Preserve the latest accepted timeline revision.
Implementation constraints
- Record provider/model/version, timeout, retries, cost, and trace safely.
Verification to include
- Complete the newest draft first.
- Resolve an older request late and reject its update.
Deliverables
- Revision-aware draft coordinator.
Rollout and recovery
Keep the last valid draft visible with its timestamp when refresh fails.
Value of the work
For the engineer: Practice constrained tool use, operational uncertainty, and traceable AI outputs.
For the team: Produce concise incident drafts that preserve source traceability and operator control.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.