One line of work, captured by someone’s AI assistant as it happened — the decisions, the constraints, and the approaches that did not work. You can read all of it, and fork it to carry on in your own account.
What is Contextaco?A fork of someone else's incident shape, continued in a direction they did not take: what happens when an incident outlives the shift that started it.
Forked from alva11s/incident-review, which is built on the Cloudflare 2019 and GitHub 2018 postmortems. Everything it established still holds here — two clocks, dead ends kept, several factors instead of one cause — and none of it is restated. That is the point of a fork: the inherited material is in the history, so this taco only has to carry what is new.
What this fork adds. The origin treats an incident as one continuous stretch of work. GitHub's own case shows the assumption breaking: a 43-second trigger and 24 hours 11 minutes of degradation. No rotation covers a day. So there is a boundary the origin has no slot for, and two things reliably die crossing it — the dead ends, which get re-run by the incoming shift, and the standing decision, which a fresh responder can reverse without ever realising it was a decision.
That is the handover type, declared here and not in the origin.
⚠️ This is a demonstration account. The fork is real and so is the added note; there is no real incident behind it.
Standing instruction for anyone working in a fork of this: before you hand over, read your own dead-end notes aloud to the person taking the shift. If you cannot, they were not written.