Definition
The handling of an exception without any change to the rule, category, workflow, or authority that produced it. A customer-service representative patches an error, a clinician works around bad software, an appeals team reverses a bad determination: each is handled, each is closed, and nothing upstream changes.
It matters because absorption is what makes exception learning invisible. Every absorbed exception improves the metric that would have caught the pattern, so an institution can be excellent at absorption and wholly incapable of learning, and the excellence is what hides the incapacity. It is the failure mode Law VII's failure-point sequence leaves unresolved when a challenge enters as a case and stops there.
Absorption is the process by which the human subsidy hides failure: the people doing the unlogged work close each case, and the record shows a case closed rather than a rule that failed.
What is institutional debris? — the explainer, with a worked example
Tests that show it is in place
- Handling an exception records whether it changed a policy, category, workflow, or authority object.
- The pattern of exceptions is queried on a schedule, not only closed case by case.
- Repeated absorption fires a review trigger upstream of the queue that clears the exceptions.
Evidence to keep
- Artifact: A queue that records exceptions as resolved cases but produces no aggregated signal.
- Behavior: An exception pattern reaching the review trigger without the trigger firing.
- Metric: Share of resolved exceptions that changed the object that produced them.
References
- Exception learning · Theory