AIROOT-001™

The SAFECHAIN™ Accountability Integrity Root Cause & Systemic Failure Analysis Framework™

Establishing the Governance Methodology for Identifying Causation, Enabling Conditions, Control Failure, Leadership Responsibility, Cultural Weakness and Systemic Accountability Failure Across AI1™–AI5™

Framework Reference: AIROOT-001™
Framework Type: Root Cause, Systemic Failure Analysis, Governance Diagnosis & Prevention Framework
Parent Framework: ACCOUNTABILITY-001™ — The SAFECHAIN™ Governance Answerability, Consequence & Institutional Accountability Framework™
Assessment Methodology: AIM-001™
Evidence Standard: AIE-001™
Scorecard: AISC-001™
Transition Framework: AIT-001™
Improvement & Restoration Programme: AIP-001™
Assurance Framework: AIA-001™
Oversight Framework: AIO-001™
Reporting Framework: AIR-001™
Monitoring Framework: AIMON-001™
Governance Review Framework: AIGR-001™
Closure & Learning Framework: AICL-001™
Recurrence Framework: AIREC-001™
Classification Architecture: AI1™–AI5™
Framework Series: SAFECHAIN™ Accountability Integrity Series
Version: 1.0
Year: 2026

1. Framework Purpose

The SAFECHAIN™ Accountability Integrity Root Cause & Systemic Failure Analysis Framework™ (AIROOT-001™) establishes a structured governance methodology for determining why an accountability failure occurred, what conditions enabled it, why existing safeguards failed to prevent or detect it, and what must change to reduce the likelihood of recurrence.

Institutions frequently investigate what happened.

They do not always investigate deeply enough to establish why it was able to happen.

An employee may make an incorrect decision.

A safeguarding concern may be missed.

Evidence may disappear.

A complaint may not be escalated.

A control may fail.

A manager may fail to intervene.

A governance body may not receive relevant information.

These may describe the visible event.

They do not necessarily explain its cause.

AIROOT-001™ therefore requires institutions to move beyond the person, decision or process closest to the failure and examine the wider conditions that created, enabled, prolonged, concealed or failed to correct it.

2. Central Question

What institutional conditions made this failure possible, allowed it to continue, prevented its detection or correction, and would permit it to happen again?

3. Governing Principle

Root-cause analysis is credible only where it moves beyond the visible event and tests the decisions, controls, incentives, culture, authority, evidence, leadership and governance conditions that enabled the failure to occur or recur.

4. Root Cause Is Not the Same as the Event

AIROOT-001™ distinguishes:

Event — What happened?

Immediate Cause — What directly produced the event?

Contributory Cause — What increased its likelihood or severity?

Governance Cause — What institutional weakness enabled or failed to prevent it?

Systemic Cause — What structural condition permits similar failure to occur repeatedly or across the institution?

5. SAFECHAIN™ Root Cause Analysis Architecture™

AIROOT-001™ establishes the:

SAFECHAIN™ Root Cause Analysis Architecture™

comprising nine stages.

RCA1 — Failure Definition

Define precisely:

• What failed;

• where;

• when;

• who or what was affected;

• consequence;

• safeguarding relevance.

RCA2 — Evidence Reconstruction

Reconstruct the event using reliable evidence.

RCA3 — Immediate Cause Analysis

Identify the condition directly associated with the failure.

RCA4 — Contributory Cause Analysis

Identify conditions that increased the probability, duration or severity of failure.

RCA5 — Governance Cause Analysis

Examine controls, authority, escalation, oversight and accountability.

RCA6 — Systemic Cause Analysis

Determine whether broader structural or institutional conditions exist.

RCA7 — Cause Verification

Test whether proposed causes are actually supported by evidence.

RCA8 — Corrective Design

Connect verified causes to appropriate intervention.

RCA9 — Monitoring & Revalidation

Test whether corrective action removed or materially reduced the underlying conditions.

6. SAFECHAIN™ Causation Traceability Chain™

AIROOT-001™ establishes:

Event → Evidence → Immediate Cause → Contributory Conditions → Governance Cause → Systemic Cause → Corrective Action → Verification → Prevention

This chain ensures remediation is connected to the causes identified rather than merely to the visible consequences.

7. Four-Layer Causation Model™

AIROOT-001™ establishes the:

SAFECHAIN™ Four-Layer Causation Model™

Layer 1 — Immediate Cause

The direct operational event or decision associated with the failure.

Layer 2 — Contributory Conditions

Factors that increased the likelihood, severity or duration of the failure.

Layer 3 — Governance Cause

Failures of controls, accountability, authority, oversight, evidence, escalation or leadership.

Layer 4 — Systemic Cause

Structural, cultural or institutional conditions capable of producing or sustaining similar failure across time, people, teams or services.

8. Layer Interaction

The layers should not be treated as mutually exclusive.

A failure may have multiple causes operating simultaneously.

For example:

Immediate cause: A safeguarding referral was not escalated.

Contributory condition: Staff responsibilities were unclear.

Governance cause: No effective escalation control existed.

Systemic cause: Organisational culture discouraged escalation that might create reputational risk.

9. SAFECHAIN™ Layered Causation Principle™

The person or process closest to the point of failure should not automatically be treated as the deepest cause of that failure.

10. Immediate Cause Test™

AIROOT-001™ establishes the:

SAFECHAIN™ Immediate Cause Test™

Ask:

What occurred immediately before the failure?

What decision, omission or system event directly contributed?

What should have happened instead?

Was the expected action reasonably possible?

What prevented it?

11. Immediate Cause Categories

Potential immediate causes include:

• Human action;

• human omission;

• procedural error;

• technological failure;

• evidence failure;

• communication failure;

• decision error;

• escalation failure;

• control failure.

12. Immediate Cause Is Not Root Cause

Identifying that an individual failed to perform an action does not establish why that failure occurred.

AIROOT-001™ requires the analysis to continue.

13. SAFECHAIN™ Stop-Too-Early Safeguard™

Root-cause analysis should not stop at the first plausible explanation where deeper institutional conditions may have materially contributed to the failure.

14. Contributory Cause Matrix™

AIROOT-001™ establishes the:

SAFECHAIN™ Contributory Cause Matrix™

Each failure should be assessed against relevant contributory domains:

People

Competence, workload, supervision, conduct, fatigue, role clarity.

Process

Procedures, workflow, handoffs, escalation, complexity.

Evidence

Availability, reliability, access, retention, traceability.

Technology

System design, access, automation, interoperability, alerts.

Resources

Capacity, staffing, funding, time.

Authority

Decision rights, delegation, role conflict, unclear responsibility.

Leadership

Direction, intervention, priorities, resourcing.

Culture

Silence, fear, normalisation, defensiveness, incentives.

Safeguarding

Vulnerability recognition, protection, escalation and response.

External Environment

External dependency, regulatory change or other relevant conditions.

15. Cause Weighting

Contributory causes may be classified as:

Primary

Materially necessary to understanding the failure.

Significant

Substantially increased risk or severity.

Contributory

Played a meaningful supporting role.

Contextual

Relevant but not materially causal.

16. SAFECHAIN™ Multi-Cause Principle™

Complex accountability failures should not be forced into a single-cause explanation where the evidence demonstrates interacting causes.

17. Governance Cause Test™

AIROOT-001™ establishes the:

SAFECHAIN™ Governance Cause Test™

The test asks whether institutional governance contributed to the failure.

Examine:

Was ownership clear?

Were decision rights appropriate?

Were controls adequate?

Was evidence available?

Was challenge possible?

Did escalation function?

Were conflicts managed?

Was safeguarding visible?

Was oversight informed?

Did leadership act?

Were consequences meaningful?

18. Governance Cause Categories

GC1 — Authority Failure

Responsibility or decision rights were unclear or inappropriate.

GC2 — Control Failure

A required control was absent, weak or ineffective.

GC3 — Evidence Failure

Decision-makers lacked reliable evidence.

GC4 — Challenge Failure

Credible dissent could not influence the process.

GC5 — Escalation Failure

Risk did not reach appropriate authority.

GC6 — Oversight Failure

Governance bodies lacked visibility or failed to intervene.

GC7 — Accountability Failure

Responsibility existed without meaningful answerability or consequence.

19. SAFECHAIN™ Governance Causation Principle™

Where an institution possessed authority to prevent, detect, escalate or correct a failure but its governance arrangements did not do so, governance causation must be examined.

20. Systemic Cause Threshold™

AIROOT-001™ establishes the:

SAFECHAIN™ Systemic Cause Threshold™

A cause should be considered potentially systemic where it:

• Exists across multiple teams or services;

• persists over time;

• affects multiple people;

• survives leadership changes;

• survives remediation;

• appears across accountability domains;

• originates in organisational design, policy, culture or governance;

• can reproduce failure independently of a particular individual.

21. Systemic Does Not Mean Organisation-Wide

A weakness can be systemic without existing everywhere.

The relevant question is whether institutional structures materially enable reproduction of the failure.

22. SAFECHAIN™ Systemic Cause Principle™

A cause is systemic where institutional arrangements materially enable the failure to reproduce, even if the failure has not yet occurred in every part of the institution.

23. Systemic Cause Indicators

Indicators may include:

• Recurrence;

• multiple affected persons;

• cross-site similarity;

• persistent control weakness;

• repeated assurance findings;

• failed remediation;

• repeated safeguarding failures;

• normalised poor practice;

• leadership tolerance;

• structural conflicts.

24. Individual-Blame Safeguard™

AIROOT-001™ establishes the:

SAFECHAIN™ Individual-Blame Safeguard™

This prevents institutional root-cause analysis from ending with an individual where broader enabling conditions have not been tested.

25. Individual Accountability Remains Relevant

The safeguard does not remove individual accountability.

Individual conduct may be a genuine causal factor.

AIROOT-001™ requires both questions:

What did the individual do?

and

What institutional conditions enabled, encouraged, failed to detect or failed to correct it?

26. SAFECHAIN™ Dual Accountability Principle™

Individual accountability and institutional accountability are not alternatives; credible analysis must examine both where the evidence supports both.

27. Individual-Blame Warning Indicators

Review is required where:

• Analysis ends with “human error”;

• one employee is removed and the matter closes;

• systemic conditions remain unexamined;

• similar failures involve different employees;

• the same process remains unchanged;

• supervision and leadership are excluded.

28. Different People, Same Failure

Where different individuals make materially similar errors, AIROOT-001™ requires institutional causation to be tested.

29. Enabling Conditions Map™

AIROOT-001™ establishes the:

SAFECHAIN™ Enabling Conditions Map™

The map identifies conditions that may not directly cause failure but make it easier for failure to occur, persist or remain concealed.

30. Enabling Condition Categories

These may include:

Opportunity

Weak Controls

Poor Visibility

Unclear Ownership

Authority Imbalance

Incentive

Fear

Silence

Normalisation

Evidence Fragmentation

Resource Pressure

Weak Challenge

Leadership Tolerance

Safeguarding Blind Spots

31. SAFECHAIN™ Enabling Condition Principle™

A condition need not directly produce failure to be governance-significant if it materially increases the institution's vulnerability to that failure.

32. Control Failure Analysis™

AIROOT-001™ establishes the:

SAFECHAIN™ Control Failure Analysis™

For every relevant control, determine:

Did the control exist?

Was it correctly designed?

Was it implemented?

Was it understood?

Was it used?

Did it operate?

Was failure detected?

Was circumvention possible?

Was effectiveness monitored?

33. Control Failure Categories

CF1 — Missing Control

No adequate control existed.

CF2 — Design Failure

The control existed but could not adequately address the risk.

CF3 — Implementation Failure

The control was designed but not properly implemented.

CF4 — Operating Failure

The control existed but failed in practice.

CF5 — Circumvention Failure

The control could readily be bypassed.

CF6 — Monitoring Failure

Control deterioration was not detected.

34. SAFECHAIN™ Paper-Control Safeguard™

A policy, procedure or control existing on paper is not evidence that the control operated effectively in practice.

35. Control Effectiveness Evidence

Evidence may include:

• Operational records;

• sampling;

• audit;

• assurance;

• interviews;

• decision records;

• monitoring data;

• incident outcomes.

36. Leadership & Oversight Cause Review™

AIROOT-001™ establishes the:

SAFECHAIN™ Leadership & Oversight Cause Review™

The review asks whether leadership or governance oversight:

• Knew;

• should reasonably have known;

• received warning;

• had authority;

• had resources;

• failed to intervene;

• delayed action;

• tolerated recurrence;

• suppressed escalation;

• failed to verify remediation.

37. Leadership Knowledge Test™

Ask:

What information reached leadership?

When?

Through which route?

What response followed?

Was the response proportionate?

38. Constructive Governance Knowledge™

AIROOT-001™ distinguishes actual knowledge from circumstances where governance systems should reasonably have made the issue visible.

39. SAFECHAIN™ Governance Visibility Principle™

Leadership cannot rely solely on lack of personal knowledge where governance systems were designed, or should reasonably have been designed, to surface the relevant risk.

40. Oversight Cause

Oversight bodies should be examined where:

• Information was available but ignored;

• reporting was inadequate;

• challenge was ineffective;

• assurance was over-relied upon;

• repeated failures were not connected.

41. SAFECHAIN™ Oversight Failure Principle™

Oversight fails not only when information is absent, but when material information is available and governance does not respond appropriately to it.

42. Cultural Cause Analysis™

AIROOT-001™ establishes the:

SAFECHAIN™ Cultural Cause Analysis™

Culture should be examined where organisational norms influence behaviour.

43. Cultural Cause Indicators

Potential indicators include:

• Fear of challenge;

• retaliation;

• silence;

• excessive hierarchy;

• reputation protection;

• target pressure;

• normalisation of poor practice;

• blame culture;

• weak safeguarding;

• avoidance of adverse evidence;

• reluctance to escalate.

44. Culture Requires Evidence

“Culture” should not become a vague explanation.

Evidence may include:

• Recurring behaviour;

• staff accounts;

• complaint patterns;

• whistleblowing evidence;

• leadership communications;

• incentive structures;

• repeated decisions;

• assurance findings.

45. SAFECHAIN™ Cultural Evidence Rule™

Cultural causation should be supported by observable patterns, incentives, behaviours or governance evidence rather than asserted as an unexplained institutional characteristic.

46. Incentive Analysis™

Institutions should examine formal and informal incentives.

These may include incentives to:

• Close complaints quickly;

• avoid escalation;

• protect reputation;

• meet targets;

• minimise reported incidents;

• suppress cost;

• preserve authority.

47. SAFECHAIN™ Incentive-Causation Question™

Ask:

What behaviour did the institution's incentives make easier, safer, more rewarding or more likely?

48. Safeguarding Root Cause Analysis

Where safeguarding is relevant, root-cause analysis must examine:

• Vulnerability recognition;

• information sharing;

• escalation;

• protective action;

• participation;

• trauma-informed response;

• leadership visibility.

49. SAFECHAIN™ Safeguarding Causation Override™

Serious safeguarding failure should not be attributed solely to frontline error without examining whether the safeguarding system itself contributed.

50. Evidence-System Root Cause

Evidence failure may arise from:

• Poor records;

• inaccessible systems;

• deletion;

• fragmented information;

• weak retention;

• unreliable data;

• absent decision trails.

51. SAFECHAIN™ Evidence-System Cause Test™

Ask:

Was the necessary evidence available?

Was it accessible?

Was it reliable?

Was it preserved?

Could decision-makers trace it?

Could challenge access it?

52. Decision-Making Root Cause

AIROOT-001™ should examine whether failure resulted from:

• Inadequate evidence;

• poor reasoning;

• authority confusion;

• conflict;

• disproportionality;

• failure to challenge;

• predetermined outcomes.

53. Challenge Root Cause

Where challenge failed, ask:

Could dissent be raised safely?

Did it reach authority?

Was it considered?

Was retaliation possible?

Was disagreement documented?

54. Conflict Root Cause

Where conflicts existed, examine:

• Disclosure;

• management;

• recusal;

• replacement;

• independence;

• decision integrity.

55. Resource Cause

Resource constraints may be causal but should not automatically excuse governance failure.

Ask:

Was the risk known?

Were resources inadequate?

Who made the resource decision?

Was safeguarding compromised?

Was the risk escalated?

56. SAFECHAIN™ Resource Accountability Principle™

Resource constraint may explain operational difficulty, but governance analysis must still identify who accepted the resulting risk and whether that acceptance was informed and proportionate.

57. Technology Cause

Technology-related causes may include:

• Poor system design;

• automation error;

• inaccessible data;

• inadequate alerts;

• interoperability failure;

• biased systems;

• weak human oversight.

58. AI and Automated Decision Systems

Where AI contributes to an accountability failure, analysis should examine:

• Data;

• model limitations;

• human oversight;

• explainability;

• escalation;

• authority;

• bias;

• monitoring.

59. SAFECHAIN™ Automation Accountability Principle™

Automation does not remove accountability; responsibility must remain traceable to the institutional decisions governing the design, deployment, oversight and use of automated systems.

60. External Cause

External conditions may contribute to failure.

However, institutions should distinguish:

External cause

from

internal failure to anticipate or manage external risk.

61. Root Cause Versus Symptom

AIROOT-001™ requires analysts to distinguish symptoms from causes.

Examples:

Symptom: High complaint volume.

Potential cause: Defective service process.

Symptom: Staff turnover.

Potential cause: Unsafe culture or workload.

Symptom: Missing records.

Potential cause: Weak evidence governance.

62. SAFECHAIN™ Symptom-Cause Test™

Ask:

If this identified factor disappeared tomorrow, would the underlying conditions still be capable of producing the failure?

If yes, deeper analysis may be required.

63. Root Cause Versus Recurrence Mechanism

A root cause explains why failure occurred.

A recurrence mechanism explains why it can continue happening.

The two may overlap but should be distinguished.

64. Recurrence Integration

AIREC-001™ evidence should inform root-cause analysis where repeated failure exists.

Recurrence may reveal causes invisible within a single incident.

65. Historical Cause Analysis

Previous events should be examined where they reveal:

• Prior warnings;

• repeated controls;

• failed remediation;

• persistent cultural conditions;

• longstanding governance weakness.

66. SAFECHAIN™ Historical Causation Principle™

Historical failure remains causally relevant where the institutional conditions that produced it remain materially present.

67. Root Cause Confidence Scale™

AIROOT-001™ establishes the:

SAFECHAIN™ Root Cause Confidence Scale™

RCC1 — Hypothesised Cause

Plausible but insufficient evidence.

RCC2 — Emerging Cause

Some supporting evidence exists.

RCC3 — Supported Cause

Evidence materially supports the causal conclusion.

RCC4 — Strongly Supported Cause

Multiple reliable evidence sources support the conclusion.

RCC5 — Verified Root Cause

The causal conclusion has been independently or robustly tested and is strongly supported.

68. Confidence Is Not Severity

A highly severe potential cause may have low evidential confidence.

A less severe cause may have high confidence.

The two should be recorded separately.

69. SAFECHAIN™ Causal Confidence Principle™

Institutions should distinguish how serious a proposed cause would be from how confident the evidence allows them to be that it is actually causal.

70. Causal Hypothesis Register™

AIROOT-001™ establishes the:

SAFECHAIN™ Causal Hypothesis Register™

Potential causes should be recorded before final conclusions.

For each hypothesis:

Proposed Cause

Supporting Evidence

Contradictory Evidence

Confidence

Further Testing

Final Status

71. Alternative Explanation Test™

Before accepting a root cause, analysts should test plausible alternatives.

72. SAFECHAIN™ Confirmation-Bias Safeguard™

Root-cause analysis should seek evidence capable of disproving the preferred explanation, not merely evidence capable of supporting it.

73. Root Cause Verification Gate™

AIROOT-001™ establishes the:

SAFECHAIN™ Root Cause Verification Gate™

A root-cause conclusion should not be treated as verified until:

• Relevant evidence has been tested;

• competing explanations have been considered;

• causal logic is traceable;

• contributory conditions are visible;

• governance causes have been tested;

• systemic causes have been considered;

• contradictions are addressed;

• confidence is recorded.

74. Verification Questions

Ask:

Does the evidence support the cause?

Does the timeline support it?

Would the cause reasonably produce the observed failure?

Is contradictory evidence explained?

Have alternative causes been tested?

Does recurrence support the conclusion?

75. Independent Verification

Enhanced independent verification should be considered where:

• Failure is serious;

• safeguarding is involved;

• senior leadership is implicated;

• systemic failure is alleged;

• AI4™ or AI5™ classification may result.

76. Root Cause to Remediation Link™

Every verified material cause should connect to remediation.

77. SAFECHAIN™ Cause-Remedy Alignment Test™

Ask:

Does the proposed remediation remove, reduce or control the cause actually identified?

If not, remediation should be challenged.

78. Symptom Remediation Risk™

Actions may appear responsive while leaving the root cause intact.

Examples include:

• Retraining without fixing defective systems;

• replacing one employee without changing enabling conditions;

• rewriting policy without testing implementation;

• issuing reminders without addressing incentives.

79. SAFECHAIN™ Cosmetic Remediation Safeguard™

Remediation that changes the appearance of the response without materially changing the conditions that produced failure should not be treated as root-cause remediation.

80. Root Cause Ownership™

Each verified material root cause should have an accountable owner.

81. Ownership Requirements

Record:

Cause

Owner

Required Intervention

Deadline

Verification

Residual Risk

82. Systemic Cause Ownership

Systemic causes should ordinarily be owned at a level with sufficient authority to change the relevant institutional architecture.

83. SAFECHAIN™ Authority-to-Remedy Principle™

Responsibility for correcting a root cause should sit with an authority capable of changing the conditions that created it.

84. Root Cause Escalation

Serious findings may require escalation through AIO-001™.

Triggers include:

• Leadership cause;

• safeguarding failure;

• systemic cause;

• repeated failed remediation;

• critical-domain failure.

85. Root Cause Reporting

AIR-001™ reporting should distinguish:

Observed Failure

Immediate Cause

Contributory Causes

Governance Cause

Systemic Cause

Confidence

Corrective Action

86. Root Cause Monitoring

AIMON-001™ should monitor whether identified causal conditions:

• Persist;

• deteriorate;

• recur;

• migrate elsewhere;

• respond to remediation.

87. Root Cause and Closure

AICL-001™ closure should consider whether material causes have been addressed.

Closure should not be based solely on completion of surface-level actions.

88. Root Cause and Recurrence

AIREC-001™ should test whether recurrence indicates:

• Incorrect root-cause identification;

• incomplete remediation;

• additional causes;

• systemic weakness.

89. SAFECHAIN™ Recurrence Reopens Causation Principle™

Material recurrence after root-cause remediation should trigger reconsideration of whether the original causal analysis was complete and correct.

90. Root Cause and AI1™–AI5™

Root-cause findings may inform classification.

AI1™

Controls and governance generally demonstrate effective causal prevention and learning.

AI2™

Limited causal weaknesses requiring improvement.

AI3™

Material governance causes or recurring control weakness.

AI4™

Serious leadership, safeguarding, critical-domain or structural causation.

AI5™

Systemic causes materially embedded within institutional architecture or culture.

91. Root Cause Does Not Automatically Determine Classification

Classification remains based on the wider Accountability Integrity evidence architecture.

AIROOT-001™ supplies causal evidence into AIM-001™, AISC-001™ and AIT-001™.

92. Root Cause Analysis Record™

AIROOT-001™ establishes the:

SAFECHAIN™ Root Cause Analysis Record™

It should contain:

Failure

Scope

Evidence

Timeline

Immediate Cause

Contributory Causes

Governance Causes

Systemic Causes

Enabling Conditions

Control Failures

Leadership Findings

Cultural Findings

Safeguarding

Alternative Hypotheses

Confidence

Verification

Corrective Action

Owner

Monitoring

93. Root Cause Decision Trail™

The analysis should preserve:

Evidence → Hypothesis → Testing → Cause → Confidence → Governance Significance → Intervention

94. Root Cause Review Independence

Persons materially implicated in a failure should not possess unilateral authority to determine its root cause.

95. SAFECHAIN™ Root Cause Independence Principle™

Those whose decisions may form part of the causal chain should not control whether those decisions are examined.

96. Participation

Where appropriate, evidence from:

• Affected persons;

• frontline staff;

• whistleblowers;

• specialists;

• independent reviewers;

should inform the analysis.

97. Affected-Person Evidence

Affected persons may possess evidence about:

• Warning signs;

• failed escalation;

• continuing harm;

• repeated behaviour;

• institutional response.

Their evidence should be assessed on its merits.

98. SAFECHAIN™ Perspective Integrity Principle™

Root-cause analysis should not be limited to the perspective of the institution whose systems are under examination.

99. Root Cause Learning

Verified causes should inform:

• Policy;

• training;

• controls;

• governance;

• safeguarding;

• monitoring;

• assurance;

• institutional learning.

100. Root Cause Prevention Cycle™

AIROOT-001™ establishes:

Failure → Investigate → Identify → Test → Verify → Correct → Monitor → Learn → Prevent

101. Root Cause Review Triggers™

Formal root-cause analysis should be considered where:

• Serious harm occurs;

• safeguarding failure occurs;

• recurrence crosses AIREC-001™ thresholds;

• critical-domain failure occurs;

• remediation repeatedly fails;

• systemic weakness is suspected;

• AI4™ or AI5™ conditions may exist.

102. Proportionality

Not every minor event requires full systemic root-cause analysis.

Depth should reflect:

• Severity;

• recurrence;

• safeguarding;

• complexity;

• systemic potential;

• public or institutional significance.

103. SAFECHAIN™ Proportionate Causation Principle™

The depth of causal analysis should be proportionate to the seriousness, recurrence and systemic potential of the accountability failure.

104. AIROOT-001™ Root Cause & Systemic Failure Integrity Test™

Before an institution accepts a root-cause conclusion, ask:

1. Has the failure been precisely defined?

2. Is the scope clear?

3. Has the evidence been reconstructed?

4. Is the timeline reliable?

5. Has the Immediate Cause Test™ been applied?

6. Has immediate cause been distinguished from root cause?

7. Has the Contributory Cause Matrix™ been applied?

8. Have people factors been considered?

9. Have process factors been considered?

10. Have evidence factors been considered?

11. Have technology factors been considered?

12. Have resource factors been considered?

13. Have authority factors been considered?

14. Have leadership factors been considered?

15. Have cultural factors been considered?

16. Have safeguarding factors been considered?

17. Have external factors been considered?

18. Have causes been appropriately weighted?

19. Has multi-causation been considered?

20. Has the Governance Cause Test™ been applied?

21. Was ownership clear?

22. Were decision rights appropriate?

23. Were controls adequate?

24. Was evidence available?

25. Was challenge effective?

26. Did escalation function?

27. Were conflicts managed?

28. Was oversight informed?

29. Did leadership respond?

30. Was accountability meaningful?

31. Has the Systemic Cause Threshold™ been tested?

32. Does the condition exist across teams or services?

33. Does it persist over time?

34. Does it affect multiple people?

35. Has it survived previous remediation?

36. Can it reproduce independently of one individual?

37. Has the Individual-Blame Safeguard™ been applied?

38. Has analysis stopped prematurely at “human error”?

39. Has individual accountability still been examined where appropriate?

40. Have institutional enabling conditions been examined?

41. Has the Enabling Conditions Map™ been completed?

42. Have weak controls been considered?

43. Has poor visibility been considered?

44. Has unclear ownership been considered?

45. Have incentives been considered?

46. Has fear or silence been considered?

47. Has evidence fragmentation been considered?

48. Has leadership tolerance been considered?

49. Has the Control Failure Analysis™ been completed?

50. Did relevant controls exist?

51. Were controls correctly designed?

52. Were they implemented?

53. Did they operate?

54. Could they be bypassed?

55. Was deterioration monitored?

56. Has the Paper-Control Safeguard™ been applied?

57. Has the Leadership & Oversight Cause Review™ been completed?

58. What did leadership know?

59. What should governance reasonably have known?

60. What warnings existed?

61. What response followed?

62. Was that response proportionate?

63. Did oversight have adequate information?

64. Did oversight act?

65. Has the Cultural Cause Analysis™ been completed?

66. Is any cultural conclusion evidence-based?

67. Have institutional incentives been examined?

68. Has reputation protection been considered where relevant?

69. Has target pressure been considered?

70. Has safeguarding causation been separately examined?

71. Has the Safeguarding Causation Override™ been considered?

72. Has evidence-system causation been examined?

73. Has decision-making causation been examined?

74. Has challenge failure been examined?

75. Have conflicts been examined?

76. Have resource constraints been examined?

77. Has responsibility for accepting resource risk been identified?

78. Has technology causation been examined?

79. Has AI or automation been examined where relevant?

80. Has human accountability for automation remained traceable?

81. Have external causes been distinguished from internal risk-management failure?

82. Have symptoms been distinguished from causes?

83. Has the Symptom-Cause Test™ been applied?

84. Has root cause been distinguished from recurrence mechanism?

85. Has AIREC-001™ recurrence evidence been considered?

86. Has relevant historical evidence been considered?

87. Has the Root Cause Confidence Scale™ been applied?

88. Is severity distinguished from causal confidence?

89. Has a Causal Hypothesis Register™ been used where appropriate?

90. Has supporting evidence been identified?

91. Has contradictory evidence been identified?

92. Have alternative explanations been tested?

93. Has the Confirmation-Bias Safeguard™ been applied?

94. Has the Root Cause Verification Gate™ been passed?

95. Is independent verification required?

96. Does remediation correspond to the verified cause?

97. Has the Cause-Remedy Alignment Test™ been passed?

98. Has cosmetic remediation been excluded?

99. Does each material cause have an accountable owner?

100. Does that owner possess sufficient authority to remedy the cause?

101. Have systemic causes been escalated appropriately?

102. Is root-cause reporting accurate?

103. Is causal confidence disclosed?

104. Is ongoing monitoring defined?

105. Does closure depend upon addressing material causes?

106. Has recurrence reopened causal analysis where necessary?

107. Has classification impact been considered?

108. Is the Root Cause Analysis Record™ complete?

109. Is the Root Cause Decision Trail™ traceable?

110. Is analysis sufficiently independent?

111. Have affected-person and frontline perspectives been considered where relevant?

112. Has learning been converted into prevention?

113. Is the depth of analysis proportionate to severity?

114. Can the institution explain not only what failed, but why its governance system allowed that failure to occur?

115. Can it demonstrate that the conditions capable of producing the same failure have been removed, reduced, controlled or made visible?

If yes, the institution has passed the:

SAFECHAIN™ AIROOT-001 Root Cause & Systemic Failure Integrity Test™

105. Framework Outcomes

Implementation of AIROOT-001™ is intended to provide:

✓ Structured root-cause investigation
✓ Four-layer causation analysis
✓ Separation of symptoms from causes
✓ Immediate and contributory cause identification
✓ Governance-cause analysis
✓ Systemic-cause identification
✓ Protection against premature individual blame
✓ Dual individual/institutional accountability
✓ Enabling-condition mapping
✓ Control-failure diagnosis
✓ Leadership and oversight analysis
✓ Cultural-cause assessment
✓ Safeguarding causal analysis
✓ Evidence-system analysis
✓ Decision and challenge analysis
✓ Resource and technology causation analysis
✓ Root Cause Confidence Scale™
✓ Alternative hypothesis testing
✓ Root Cause Verification Gate™
✓ Cause-remedy alignment
✓ Root-cause ownership
✓ Recurrence integration
✓ Prevention and institutional learning

106. Governing Statement

Institutions often find the easiest cause first.

Someone failed to follow procedure.

Someone made the wrong decision.

Someone did not escalate.

Someone did not record something.

Someone made a mistake.

Sometimes that explanation is accurate.

But it is rarely sufficient to establish the integrity of the system surrounding that person.

AIROOT-001™ therefore asks what happened behind the failure.

Was the procedure workable?

Was the person trained?

Was responsibility clear?

Was the evidence available?

Was there enough time?

Could they challenge?

Could they escalate?

Would anyone listen?

Were the controls real or merely written?

Did managers know?

Did leadership know?

Should they have known?

Had it happened before?

Had someone warned the institution?

Had remediation already supposedly occurred?

Did organisational incentives make the wrong behaviour easier than the right behaviour?

And if the individual were replaced tomorrow, could the same institutional conditions cause somebody else to fail in substantially the same way?

That final question matters.

Because removing a person does not repair a system.

Rewriting a policy does not prove a control works.

Training does not prove behaviour changed.

An apology does not identify causation.

And a completed investigation does not establish that the conditions which produced the failure have disappeared.

The AIROOT-001™ sequence is therefore:

Define → Reconstruct → Diagnose → Connect → Test → Verify → Correct → Monitor → Prevent

The objective is not to remove individual responsibility.

It is to prevent individual responsibility from being used to conceal institutional responsibility.

A mature accountability system must be capable of holding both truths at once:

An individual may have failed.

And the institution may have created, enabled, tolerated or failed to correct the conditions in which that failure occurred.

Root-cause analysis reaches integrity only when the institution is prepared to examine both.

Copyright and Intellectual Property Notice

© 2026 Samantha Avril-Andreassen. All Rights Reserved.

AIROOT-001™ — The SAFECHAIN™ Accountability Integrity Root Cause & Systemic Failure Analysis Framework™ is an original governance causation, root-cause analysis, systemic-failure diagnosis, enabling-condition, control-failure, leadership-causation, cultural-analysis and prevention framework developed and authored by Samantha Avril-Andreassen, LLB (Hons), LLM, LPC, FRSA, Founder of SAFECHAIN™.

AIROOT-001™ forms part of the SAFECHAIN™ Accountability Integrity Series and operates in conjunction with ACCOUNTABILITY-001™, AI1™–AI5™, AIM-001™, AIE-001™, AISC-001™, AIT-001™, AIP-001™, AIA-001™, AIO-001™, AIR-001™, AIMON-001™, AIGR-001™, AICL-001™ and AIREC-001™.

The original expression, selection, arrangement, architecture, terminology, causal methodology, layered causation architecture, contributory-cause analysis, governance-cause methodology, systemic-cause methodology, individual-blame safeguards, enabling-condition mapping, control-failure analysis, leadership and oversight review, cultural-cause methodology, causal-confidence architecture, verification mechanisms, causal records, tests and associated implementation materials contained within this publication constitute proprietary intellectual property.

This includes, where original to AIROOT-001™, the SAFECHAIN™ Root Cause Analysis Architecture™, Causation Traceability Chain™, Four-Layer Causation Model™, Layered Causation Principle™, Immediate Cause Test™, Stop-Too-Early Safeguard™, Contributory Cause Matrix™, Multi-Cause Principle™, Governance Cause Test™, GC1™–GC7™ Governance Cause Categories, Governance Causation Principle™, Systemic Cause Threshold™, Systemic Cause Principle™, Individual-Blame Safeguard™, Dual Accountability Principle™, Enabling Conditions Map™, Enabling Condition Principle™, Control Failure Analysis™, CF1™–CF6™ Control Failure Categories, Paper-Control Safeguard™, Leadership & Oversight Cause Review™, Governance Visibility Principle™, Oversight Failure Principle™, Cultural Cause Analysis™, Cultural Evidence Rule™, Incentive-Causation Question™, Safeguarding Causation Override™, Evidence-System Cause Test™, Resource Accountability Principle™, Automation Accountability Principle™, Symptom-Cause Test™, Historical Causation Principle™, Root Cause Confidence Scale™, RCC1™–RCC5™ Confidence Levels, Causal Confidence Principle™, Causal Hypothesis Register™, Confirmation-Bias Safeguard™, Root Cause Verification Gate™, Cause-Remedy Alignment Test™, Cosmetic Remediation Safeguard™, Authority-to-Remedy Principle™, Recurrence Reopens Causation Principle™, Root Cause Analysis Record™, Root Cause Decision Trail™, Root Cause Independence Principle™, Perspective Integrity Principle™, Root Cause Prevention Cycle™, Root Cause Review Triggers™, Proportionate Causation Principle™ and AIROOT-001™ Root Cause & Systemic Failure Integrity Test™, together with associated materials.

No part of this publication may be reproduced, copied, republished, adapted, translated, distributed, licensed, sublicensed, sold, commercially exploited or incorporated into another governance framework, root-cause methodology, accountability architecture, safeguarding framework, investigation methodology, audit system, assurance system, certification scheme, accreditation programme, consultancy methodology, training product, artificial-intelligence system, analytics platform, software product or derivative commercial offering without prior written permission from the applicable rights holder, except to the extent otherwise permitted by applicable law.

Publication or public accessibility of AIROOT-001™ does not grant authority to conduct or issue official SAFECHAIN™ root-cause findings, systemic-failure determinations, AI1™–AI5™ classifications, assessments, assurance opinions, certifications, accreditations, governance ratings, SAFECHAIN™ Seals or credentials.

No unauthorised person or organisation may represent itself as a SAFECHAIN™ authorised root-cause assessor, investigator, auditor, verifier, assurance provider, certification body, accreditation body, implementation partner or training provider without express authorisation under applicable SAFECHAIN™ governance and licensing arrangements.

References within AIROOT-001™ to generally established concepts including root-cause analysis, causation, human error, organisational culture, controls, systems thinking, safeguarding, remediation, monitoring and organisational learning do not constitute claims of exclusive ownership over those underlying concepts.

The proprietary claim relates to the original SAFECHAIN™ expression, selection, arrangement, architecture, terminology, methodologies, classifications, tests, scales, maps, gates, safeguards, records and framework materials developed by the author.

The use of the ™ symbol identifies names, concepts, methodologies and framework identifiers being asserted as proprietary brand or framework designations. It does not, by itself, constitute a representation that any designation has been registered as a trade mark in any jurisdiction.

Nothing within AIROOT-001™ should be interpreted as legal advice, statutory guidance, regulatory approval, governmental accreditation, judicial determination, finding of misconduct or determination of legal liability. The framework does not replace applicable law, regulation, statutory safeguarding duties, professional standards, formal investigative procedures, employment processes, data-protection obligations or regulatory requirements.

An AIROOT-001™ causal finding, systemic-failure finding, confidence classification or related AI1™–AI5™ classification does not, by itself, establish fraud, dishonesty, negligence, professional misconduct, criminal responsibility, regulatory breach, discrimination, bad faith, breach of statutory duty or other legal liability.

AIROOT-001™ is a governance root-cause and systemic-failure analysis framework and should be applied proportionately, independently and consistently with the lawful authority, evidence environment, safeguarding responsibilities and regulatory context of the institution concerned.

Author and Framework Developer:
Samantha Avril-Andreassen, LLB (Hons), LLM, LPC, FRSA
Founder — SAFECHAIN™

Framework: The SAFECHAIN™ Accountability Integrity Root Cause & Systemic Failure Analysis Framework™
Framework Reference: AIROOT-001™
Parent Framework: ACCOUNTABILITY-001™
Classification Architecture: AI1™–AI5™
Framework Series: SAFECHAIN™ Accountability Integrity Series
Version: 1.0
Year: 2026

© 2026 Samantha Avril-Andreassen. All Rights Reserved.