The box nobody reboots is a control gap with an owner.
Somewhere in your estate is a system that works because one person remembers why it must never be touched on Tuesdays.
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.
System ownership and incident decisions live in individuals, which is an operational risk that shows up during an outage.
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.
Procedural and system context stays in place through turnover and incidents. Kept. Keep the knowledge behind the work.
Tribal infrastructure knowledge is a finding waiting for an auditor: the legacy job that feeds the ERP, the firewall rule with no ticket, the recovery procedure that exists as one engineer's muscle memory. When that engineer leaves, your continuity plan quietly becomes fiction.
Kept captures what your team knows, in their words, and keeps it as cited memory behind real access control: people see what they are permitted to see, with answers designed to name available sources and make missing evidence clear. Review important answers. Continuity you can evidence, not just assert.
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.