InquirySpec - Ontological Boundary: Causal_Repair is the correction pathway for tracing failure back through action, context, and system design. - Not This: Not blame assignment by default. - Doctrine Dependencies: Observation_Interpretation_Application, Accountability_Assessment.
Working Definition
Causal Repair is the disciplined movement from consequence to correction. It begins when reality exposes a burden: a workflow breaks, a person absorbs hidden cleanup, a record contradicts the official story, a model fails in use, trust thins, or a decision produces consequences that were not named when the decision was made.
The repair question is not first, "Who can we punish?" It is, "What produced this consequence, and what would have to change for the burden not to recur?" That question can include personal action, but it does not begin by reducing the situation to a single person. It traces through action, context, incentives, missing artifacts, communication patterns, authority boundaries, and system design.
Causal Repair requires a loop. Observation receives the consequence. Interpretation asks what source, pattern, or constraint made the consequence likely. Application commits a bounded correction. The correction then returns to Reality-Contact: did the burden move, shrink, intensify, disappear, or become easier to discuss?
The concept is repair-oriented because causality without repair becomes accusation, while repair without causality becomes theater.
The Phenomenological Problem
Groups under pressure often oscillate between two bad defaults. The first is blame reflex: a consequence appears, and the system searches for the nearest actor who can absorb responsibility. The second is causal fog: the consequence is acknowledged, but no one is allowed to trace it because doing so would slow the workflow, unsettle authority, or reveal that the burden has been displaced onto people with less power.
Both defaults are products of systemic gravity. Causal inquiry is metabolically expensive. It asks people to preserve context, examine assumptions, distinguish evidence from narrative, and keep dialogue open long enough for a pattern to become visible. When the work system offers no scaffold for that process, even careful people drift toward simpler moves: close the ticket, assign the fault, rewrite the story, or call the outcome unavoidable.
This is how unresolved consequences become culture. The same friction returns under different names. The same people carry the cleanup. The same metrics certify progress while the lived system becomes harder to repair. The problem is not that the group lacks information. The problem is that the group lacks a legitimate pathway from consequence to cause to correction.
Causal Repair names that pathway.
The Engineering Anchor
The method anchor is Observation, Interpretation, Application. Observation starts with the consequence as it appears in reality, not as the institution prefers to describe it. Interpretation traces the consequence through context: source, visibility, distribution, evidence quality, and the conditions that shaped the available choices. Application then makes the smallest correction that is consequential enough to test the interpretation.
The accountability anchor is Accountability Assessment. Accountability assessment separates three things that are often collapsed: the consequence that happened, the evidence that makes the consequence assessable, and the dialogue through which people interpret and repair the consequence together. This separation matters because a system can have data without repair, dialogue without evidence, or punishment without causal understanding.
Causal Repair uses that separation as a guardrail. If a burden is visible but the source is misattributed, the repair will likely intensify the problem. If evidence exists but affected people cannot challenge or contextualize it, the evidence becomes surveillance rather than repair. If dialogue is warm but does not produce an accountable artifact, the group may feel relieved while the causal structure remains unchanged.
The practical sequence is:
- Name the observable consequence.
- Identify who or what is carrying the burden.
- Gather evidence that connects the burden to actions, conditions, artifacts, or design choices.
- Interpret the pattern without collapsing immediately into blame or absolution.
- Commit a bounded correction.
- Return to reality-feedback to see whether the correction changed the burden.
The loop stays humble. A repair is not proven by the confidence of the explanation. It is tested by the consequences that follow.
Boundary Conditions
Causal Repair is not blame assignment by default. Personal responsibility may become visible during the process, but the method does not begin by deciding where guilt belongs. It begins by tracing consequence.
It is not absolution by system complexity. Complex conditions can shape an action without erasing agency. A humane repair pathway can acknowledge systemic pressure, missing scaffolds, and constrained choice while still asking what each entity did, what the action revealed, and what must change.
It is not root-cause theater. Some failures do not have a single root. A causal field may include incentives, timing, tools, habits, silence, interface design, unmaintained records, and social risk. The goal is not to find the one final cause. The goal is to find the smallest honest correction that changes the next cycle.
It is not closure theater. A report can close while the burden remains. A meeting can feel resolved while the same consequence is quietly redistributed. Causal Repair remains incomplete until the correction returns to Reality-Contact.
It is not a substitute for judgment. The method can preserve evidence and structure dialogue, but people still have to interpret the situation and decide what repair requires.