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?What two of the best-documented outages in public record show about carrying an incident: Cloudflare's 2019 regex outage, and GitHub's 43-second partition.
Read against Cloudflare's 2 July 2019 postmortem and GitHub's .
Four things in those two documents are worth more than any advice about postmortems:
Each note below takes one of those and says what it implies for the shape of an incident context. The slots are the reusable part: fork this as a recipe (taco_fork with content="recipe") to get them with none of this text.
Standing instruction for anyone working in a fork of this: write into it live and badly during the incident. Both postmortems here are good because someone recorded the wrong turns while they were still wrong; by the next morning you remember the path that worked and have already forgotten the others.