The runbook is fiction. The truth is on call.
Your incident response works because the same three people always answer. That is not a process. That is luck with a rota.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
Somebody knows why that firewall rule exists. They left in the spring, and nobody dares remove it.
You’re the escalation path for access questions because the procedure was never written down.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in a jar that’s yours.
A new admin asks whether rule 41 can go. Kept answers with the reason and the risk, cited to the engineer who set it.
Access questions stop routing through you. Kept. Keep the knowledge behind the work.
Every environment accumulates truths that never reach the wiki: the service that must start second, the alert that lies, the vendor escalation path that actually works. On-call quality depends on who picks up, and cross-training means hoping the veteran enjoys explaining things at 2am.
Kept interviews your engineers about how the estate actually behaves and keeps their answers cited and queryable. The next incident gets the veteran's knowledge without the veteran's phone. You see coverage across the team. It does not score your engineers, ever.
Keeping a knowledge item does not promise permanent access to its original transcript. Sources can become unavailable after retention or removal. Check what evidence is available before relying on an answer.
Read personal and workspace controls. The overview above is available as text; explore the guided text walkthrough for a step-by-step example.