Institutional debris is the record of what people actually did to keep a formal system functioning: workarounds, overrides, tickets, grievances, and exception codes.
Institutional debris is the evidentiary record that grows around a formal process as people compensate for what it cannot represent: workaround logs, manual overrides, support tickets, grievance files, exception codes, shadow spreadsheets, repeated data corrections, escalation paths, staff notes, informal procedures, remediation records, and patterns of abandonment.
Formal documentation describes the intended process. The debris describes the second process that grew around the intended process to keep it functioning. Where the two diverge is where the formal representation stops working, which is the datum an audit needs most and the one policies never record.
Canonical entry: What is Institutional Debris? in the glossary.
A benefits workflow documents one intake form and one review step. The debris around it shows something else: caseworkers keep an unofficial spreadsheet of cases the system mangles, one employee is famous for fixing impossible cases, applicants have learned that writing the true reason for a job loss produces a denial, and the exception code for 'manual review' fires forty times a week. Each artifact is evidence about the formal system that no policy document contains.
Implementation
Unique operational detail to help this concept stand on its own in policy, procurement, and review workflows.
Workaround logs, override records with rationale and consequence, exception-code frequencies, grievance and appeal files, shadow spreadsheets, support-ticket categories, repeated data corrections, staff notes, and systems that were quietly abandoned.
Debris outranks formal documentation on the question it speaks to, because it records what the system does rather than what it says it does. A policy that says users may appeal is weak evidence; the history of actual appeals is stronger.
A recurring workaround raises a presumption of upstream design failure, rebuttable by showing the adaptation is preference rather than compensation. Organizations read workarounds as resilience; the debris supports the opposite reading — rigidity subsidized by human flexibility.
Draw system boundaries around consequences, not organizational ownership. The boundary of a consequential system is whoever carries what it cannot represent, which is rarely the party that operates it: the customer's repair labor, the nurse's overrides, and the hidden moderation queue are all inside the system.
Theory
Why handling exceptions is not the same as learning from them, and what the trajectory from failure to revision looks like.
Doctrine
The people who absorb a system's errors are usually the first to know about them; the debris is where their knowledge accumulates.
Eval
Test whether the exceptions an institution handles change the machinery that produced them.
No. It removes documentation's monopoly. The intended process is one source; the debris around it is the other. An audit that reads only the intended process grades the institution on its own description.
Sometimes, and the presumption is rebuttable. But the burden sits with the institution to show that. Repeated adaptation around the same defect is a measurement of the mismatch between the formal system and the world, and reading it as resilience is how absorbed labor becomes an invisible subsidy.