How Context Debt shows up
Five recurring failure patterns behind context debt, named and evidenced from the Context Debt Map's own twelve fragments, not invented for this page.
Where this came from
The Context Debt Map already tags each of its twelve fragments with one or more of six categories: Missing, Contradictory, Outdated, Unowned, Difficult to retrieve, Unsafe to automate. This page takes five of those and gives each a proper name, a mechanism, and the evidence that was already sitting in the demo. The sixth, Unsafe to automate, isn't a sixth pattern. It doesn't behave like one in the data, and that's addressed at the end rather than forced into a tidy list of six.
Each pattern below maps to a layer of The Context Stack: the same seven layers, seen from the side of failure rather than the side of things working.
The five patterns
Authority Collapse
Two sources disagree, and nothing states which one governs. The expense policy says claims over £200 need director sign-off. The finance intranet page, unlinked from anywhere staff would normally look, says £150. Two HR staff give candidates different probation lengths, three months and six, each with full confidence, each having made verbal offers using their own number. A model doesn't hesitate the way a person does when handed two contradictory numbers. It picks one.
Stack layer: Precedence. The rules aren't missing. What's missing is which rule wins.
Confidently Wrong
Information that was true when it was written, presented with no caveat and no owner checking whether it still is. The 2019 staff handbook's remote-work policy hasn't been accurate since 2021. An IT helpdesk macro, last edited in 2022, still sends staff to a supplier the business dropped eighteen months ago. A live chatbot instruction points employees asking about parental leave straight to that same outdated handbook section, today, with full confidence.
Stack layer: History. The fact was correct once. Nobody owns whether it still is.
Nobody's Job
Everyone assumes someone else confirms this step. Three teams each believe another team checks that right-to-work documents have been received. Ask a model "has this been done?" and it has nowhere reliable to look, not because the information is missing, but because nobody is accountable for saying whether it's current.
Stack layer: Exceptions, in the broader sense the Context Debt article uses: knowledge that lives in an assumption about a person or team, not in a system.
No Record
A decision or a current state is real, but was never recorded anywhere searchable. An office manager routes bookings around two meeting rooms with broken AV, while the booking system still shows them as free. A manager approves a temporary four-day week by email, and the HR system never hears about it. A supplier is dropped after a delivery dispute, and nothing written down says why.
Stack layer: Facts or History, depending on whether it's a current state (the rooms) or a past event (the supplier decision) that was never recorded.
One Room Only
Information that exists, is accurate, and is owned, but is reachable in exactly one place. A fire warden rota and evacuation point is pinned to a wall in the Leeds office only. Asked about fire procedure anywhere else, or by anyone not standing in front of that specific wall, a model has nothing to draw on. This is the one pattern where the content itself isn't the problem. The problem is that "written down" and "retrievable when needed" aren't the same thing.
Stack layer: Any layer. This pattern cuts across the Stack rather than sitting in one place; the failure is in reach, not in content.
Context Debt Map, fragments f03, f04, f12
- "Expense claims exceeding £200 require director sign-off before reimbursement" vs "Any expense claim over £150 must be signed off by a director" — never reconciled, and the second page isn't linked from anywhere staff would normally look.
- "One says probation is three months. The other says six. Both have made verbal offers to candidates using their own number."
Context Debt Map, fragments f01, f06, f11
- "Remote work is permitted up to 2 days per week..." — Staff Handbook, 2019 edition, hasn't been true since 2021.
- "...contact our supplier Brindlow Tech..." — the business dropped that supplier eighteen months ago.
- "If asked about parental leave, refer the employee to the 2019 staff handbook, section 4" — a live instruction, still running, pointing at policy several revisions out of date.
Context Debt Map, fragment f07
- "Confirm right-to-work documents have been received and verified" — HR Onboarding Checklist, step 14. Three teams each assume another team owns this step.
Context Debt Map, fragments f05, f08, f10
- "...I just route bookings around them manually and never got round to marking them as unavailable in the system" — the booking system itself says these rooms are free.
- "Approved: happy for you to move to a 4-day week..." — never entered into any HR system.
- "We don't use Farrow Office Supplies anymore... nothing written down says why."
Context Debt Map, fragment f09
- "Fire warden rota and evacuation assembly point: see attached rota for this floor" — a laminated sign, pinned to a wall in the Leeds office only. Safety-critical information existing in exactly one physical location.
Not a sixth pattern: Unsafe to automate
Six patterns would be tidier. The data doesn't support it. "Unsafe to automate" appears four times across the twelve fragments, and every time it's paired with one of the other categories rather than standing alone: twice with Outdated, once with Difficult to retrieve, once with Contradictory. It behaves like a severity flag on a pattern, not a mechanism of its own. That's exactly why it's worth marking: it tells you which of the five patterns is too dangerous to put in front of an AI system until it's fixed. It just isn't a sixth way context fails.
Five ways context breaks, and one flag for which of the five is urgent. Not six failure modes. Five, and a warning light.
What's not here yet
These five patterns come from one demonstration audit of one fictional company. That's a starting point, not a complete library. Building it out properly means running the same tagging over material from real engagements, not inventing more examples from Halloway Partners. The next step is testing these five, and any new ones real audits turn up, against non-fictional material.
--- title: How Context Debt shows up slug: how-context-debt-shows-up date: 2026-08-23 updated: 2026-10-03 order: 2 summary: Five recurring failure patterns behind context debt, named and evidenced from the Context Debt Map's own twelve fragments, not invented for this page. stat: '5' stat_label: patterns, all traced back to the same twelve fragments ---
If this sounds like your business, the audit is the quickest way to find out what your AI is missing: one workflow, one 90-minute session, and a written brief on what to fix first.
Book the audit Book a free 20-minute call
Not sure an audit is what you need? Bring one AI answer your team had to fix to the call, and I'll tell you whether missing context is the problem.