DEPENDENCYRISK-001™
The SAFECHAIN™ Institutional Dependency Creation, Service-Induced Vulnerability & Exit-Risk Framework™
Framework Reference: DEPENDENCYRISK-001™
Framework Type: Institutional Governance, Dependency Risk, Safeguarding, Service Design, Vulnerability, Access & Systems Reform
Framework Series: SAFECHAIN™ Justice & Institutional Integrity Series™
Parent Architecture: SAFECHAIN™ Governance Architecture™
Version: 1.0
Year: 2026
1. Framework Purpose
DEPENDENCYRISK-001™ establishes a structured governance methodology for identifying when an institution, service, process or system creates, increases or preserves dependency in a way that reduces a person's practical ability to challenge decisions, access alternatives, leave a process, protect their interests or secure remedy.
The framework addresses a critical governance problem:
An institution can become part of a person's vulnerability not only by failing to help, but by becoming the sole route through which essential needs, information, rights or resources can be accessed.
That dependency may arise around:
housing;
finance;
safeguarding;
healthcare;
evidence;
legal process;
identity documentation;
welfare;
education;
immigration;
digital access;
complaints;
redress;
information.
DEPENDENCYRISK-001™ therefore examines not only whether a service exists, but whether access to that service creates an institutional power imbalance.
2. Institutional Dependency Creation™
SAFECHAIN™ defines Institutional Dependency Creation™ as:
The creation or intensification of practical dependence upon an institution, service, process or decision-maker because that system controls access to resources, rights, information, evidence, safety, housing, finance, remedy or another essential function.
3. Service-Induced Vulnerability™
Defined as:
Vulnerability created, increased or prolonged by the design, operation, accessibility, delay, rigidity or dependency structure of an institutional service.
4. Exit Risk™
Defined as:
The practical risk arising where disengaging from, challenging or leaving an institutional process may result in loss of essential support, access, rights, information, protection or remedy.
5. Key Question
Has the institution become a source of dependency that reduces the person's practical ability to challenge, disengage or obtain remedy?
6. Core Architecture
Need → Institutional Control Point → Dependency → Reduced Alternatives → Vulnerability → Exit Risk → Safeguard → Independence Restoration → Verification
Expanded:
Need → Access → Institutional Gatekeeping → Dependency Formation → Alternative Reduction → Power Imbalance → Challenge Risk → Exit Risk → Protective Design → Independence Restoration → Review
7. Core Principle
A service can be technically available while still creating dependency risk if access, information, remedy or essential resources remain controlled by a single institutional route with insufficient alternatives or challenge mechanisms.
8. SAFECHAIN™ Institutional Dependency Architecture™
IDA1 — Need
Identify the essential need or right.
IDA2 — Access Route
Identify how the person obtains it.
IDA3 — Institutional Control Point
Identify who controls access.
IDA4 — Dependency Formation
Assess whether alternatives are reduced.
IDA5 — Vulnerability Increase
Determine whether dependency creates practical risk.
IDA6 — Challenge Constraint
Assess whether the person can safely challenge decisions.
IDA7 — Exit Risk
Determine consequences of disengagement.
IDA8 — Safeguard
Introduce protections against dependency misuse.
IDA9 — Independence Restoration
Increase alternative routes and autonomy.
IDA10 — Verification
Confirm that dependency risk has materially reduced.
9. Institutional Control Point™
Defined as:
A point within a system where access to an essential resource, decision, document, right or remedy depends upon institutional approval, processing or action.
Examples include:
housing allocation;
benefit decision;
bank access;
complaint acceptance;
safeguarding referral;
evidence disclosure;
healthcare referral;
legal authorisation;
account access;
identity verification.
10. Control Point Test™
Ask:
What can this institution prevent, delay, approve, release or withhold that materially affects the person's ability to act independently?
11. Gatekeeping Power™
Defined as:
The practical power created by controlling access to a necessary resource, process or outcome.
12. Gatekeeping Power Test™
Assess:
Need Importance + Alternative Scarcity + Decision Discretion + Delay Consequence
13. Single-Route Dependency™
Defined as:
A condition in which a person has only one practical institutional route to obtain an essential need or remedy.
14. Single-Route Dependency Test™
Ask:
If this route fails, what realistic alternative remains?
15. No-Alternative Alert™
Triggered where failure of one institutional pathway leaves the person without a meaningful substitute.
16. Alternative Scarcity™
Defined as:
The absence or practical weakness of alternative providers, appeal routes, decision-makers, services or support mechanisms.
17. Alternative Scarcity Test™
Assess:
availability;
accessibility;
affordability;
geographical reach;
eligibility;
waiting time;
informational access;
legal feasibility.
18. Institutional Monopoly Risk™
Defined as:
The governance risk arising where one institution or process possesses dominant practical control over an essential outcome.
19. Monopoly Risk Test™
Ask:
Does the institution have sufficient checks, challenge routes and independent review to counterbalance its control over the essential resource?
20. Dependency Severity Classification™
DR1 — Low Dependency
Meaningful alternatives exist.
DR2 — Emerging Dependency
Alternatives are limited.
DR3 — Material Institutional Dependency
The institution controls an important practical outcome.
DR4 — Serious Dependency
Challenging or leaving creates substantial risk.
DR5 — Critical Dependency
The person cannot realistically secure the essential need outside the controlling institutional route.
21. Service-Induced Vulnerability Test™
Ask:
Would the person be less vulnerable if the service were designed or administered differently?
22. Dependency Amplification™
Defined as:
An increase in dependency caused by institutional delay, procedural complexity, poor accessibility, rigid eligibility or repeated failure.
23. Dependency Amplification Test™
Compare:
Dependency at Entry → Dependency After Institutional Engagement
24. Delay-Induced Dependency™
Delay may increase reliance where the person:
loses financial options;
loses housing alternatives;
becomes more unwell;
loses evidence;
becomes procedurally trapped;
cannot access another service.
25. Delay Dependency Test™
Ask:
Did institutional delay reduce the person's available alternatives?
26. Procedural Dependency™
Defined as:
Dependence created because the person cannot progress without navigating a complex institutional process controlled by the institution itself.
27. Procedural Dependency Test™
Ask:
Can the person realistically progress without specialist knowledge, repeated institutional assistance or internal approval?
28. Information Dependency™
Defined as:
Dependence created where the institution controls information necessary for the person to understand, challenge or progress their own case.
29. Information Dependency Test™
Ask:
Can the person make an informed decision without information held by the institution?
30. Evidence Dependency™
Defined as:
Dependence upon an institution for documents, records, transcripts, data or other material necessary to establish a person's position or exercise a right.
31. Evidence Dependency Test™
Ask:
Does the institution control access to evidence necessary for meaningful participation or challenge?
32. Remedy Dependency™
Defined as:
Dependence upon the same institution that created or contributed to the problem for access to correction, complaint or remedy.
33. Remedy Dependency Test™
Ask:
Is the institution effectively both the subject of the complaint and the gatekeeper of the remedy?
34. Internal-Remedy Monopoly™
Defined as:
A condition in which meaningful redress depends almost entirely upon internal processes controlled by the institution being challenged.
35. Independent Remedy Test™
Ask:
Is there a genuinely independent and accessible route of review?
36. Challenge Dependency™
A person may become dependent on institutional goodwill precisely when challenging that institution.
37. Challenge Risk Test™
Ask:
Could challenging the institution reasonably jeopardise access to the service, resource or decision on which the person depends?
38. Retaliatory Dependency Risk™
Defined as:
The perceived or actual risk that challenge may affect ongoing access to an essential institutional function.
39. Retaliatory Dependency Alert™
Triggered where the person reasonably believes that complaining, appealing or challenging may threaten access or cooperation.
40. Silence-by-Dependency™
Defined as:
Reduced willingness to complain, challenge or disclose because the person depends upon the institution for an essential need.
41. Silence-by-Dependency Test™
Ask:
Would the person be more willing to challenge if they were not dependent upon this institution?
42. Exit-Risk Architecture™
Exit risk should assess:
What happens if the person leaves, disengages, refuses, appeals, transfers or stops cooperating?
43. Exit Consequence Domains™
Potential consequences include:
loss of housing;
loss of financial support;
delayed healthcare;
loss of evidence;
loss of legal participation;
loss of protection;
interrupted education;
account restriction;
loss of administrative status.
44. Exit Cost Test™
Ask:
What practical cost does the person bear for disengaging from the institutional process?
45. Institutional Exit Barrier™
Defined as:
A practical, procedural, financial, informational or safeguarding barrier that prevents a person from leaving an institutional pathway without disproportionate loss.
46. Exit Barrier Test™
Assess:
transferability;
portability;
waiting periods;
eligibility;
cost;
information access;
record access;
continuity of support.
47. Lock-In Effect™
Defined as:
A condition in which the cost of leaving an institutional service becomes so high that continued participation is effectively compelled.
48. Lock-In Test™
Ask:
Is participation technically voluntary but practically unavoidable?
49. Forced Continuation Risk™
Defined as:
The risk that a person remains within a failing institutional process because available alternatives are materially worse or inaccessible.
50. Choice Integrity Test™
Ask:
Is the person's continued engagement a genuine choice, or the least harmful available option?
51. Institutional Manufactured Choice™
Defined as:
A decision that appears voluntary but is materially shaped by institutional dependency, restricted alternatives or disproportionate exit costs.
52. Manufactured Choice Test™
Compare:
Options Presented → Options Actually Available → Consequences of Each Option
53. Dependency–Power Relationship™
The more essential the need and the fewer the alternatives, the greater the institutional power imbalance.
54. Dependency Power Index™
Conceptually assess:
Essentiality × Alternative Scarcity × Gatekeeping Power × Exit Cost
55. Dependency Power Classification™
DP1 — Balanced
DP2 — Limited Institutional Advantage
DP3 — Material Power Imbalance
DP4 — Serious Dependency Power
DP5 — Critical Institutional Control
56. Institutional Vulnerability Creation™
Defined as:
A worsening of vulnerability caused directly or indirectly by institutional structure, process or delay.
57. Vulnerability Creation Test™
Ask:
Did institutional engagement create a new vulnerability that was not present at entry?
58. Vulnerability Preservation™
Defined as:
Failure to reduce a vulnerability that the institution has sufficient power or responsibility to address.
59. Vulnerability Preservation Test™
Ask:
Did the system keep the person dependent when a reasonable alternative or safeguard could have reduced that dependency?
60. Dependency Cascade™
One dependency may create another.
Example:
Housing Dependency → Location Constraint → Employment Loss → Financial Dependency
61. Dependency Cascade Test™
Map:
Initial Dependency → Consequence → Secondary Dependency → Additional Vulnerability
62. Cross-System Dependency™
A person may become dependent across multiple institutions simultaneously.
Examples:
Housing + Benefits + Healthcare + Court
63. Cross-System Dependency Test™
Ask:
Do decisions in one system materially constrain the person's ability to access alternatives in another?
64. Dependency Compounding™
Defined as:
The increase in vulnerability created when multiple institutional dependencies reinforce one another.
65. Compounding Test™
Ask:
Does failure in one institutional domain increase dependency elsewhere?
66. Multi-Institution Dependency Classification™
MID1 — Single Limited Dependency
MID2 — Two Connected Dependencies
MID3 — Material Multi-System Dependency
MID4 — Serious Dependency Compounding
MID5 — Entrenched Institutional Dependency Architecture
67. Dependency Chronology™
Record:
Need → Institutional Entry → Delay/Decision → Alternative Reduction → Dependency Increase → Consequence
68. Dependency Duration™
Measure:
Dependency Start → Current/End Point
Long-term dependency may materially alter risk.
69. Dependency Persistence Test™
Ask:
Has dependency reduced over time, remained static or become more entrenched?
70. Dependency Recovery Deficit™
Defined as:
The failure to restore independence after the institution has addressed the immediate problem.
71. Independence Restoration Test™
Ask:
Has the person regained practical alternatives, information, agency and exit capacity?
72. Institutional Independence Restoration™
May involve:
alternative providers;
portability;
independent advice;
transparent information;
evidence access;
appeal mechanisms;
advocacy;
reduced gatekeeping;
transfer rights;
time-limited dependency;
financial independence.
73. Independence-by-Design™
Institutional services should be designed to reduce avoidable dependency wherever possible.
74. Dependency Prevention Principle™
Institutions should not make themselves more necessary than the legitimate purpose of the service requires.
75. Dependency Safeguard Architecture™
Identify Control Point → Assess Dependency → Map Alternatives → Assess Exit Risk → Reduce Gatekeeping → Preserve Challenge → Increase Portability → Verify Independence
76. Control Point Register™
Record:
institutional function;
essential resource;
gatekeeper;
decision authority;
alternative route;
dependency level.
77. Dependency Risk Register™
Record:
dependency;
cause;
severity;
duration;
exit consequence;
safeguard;
owner.
78. Exit Barrier Register™
Record:
barrier;
affected right/service;
consequence;
necessity;
proportionality;
remediation.
79. Alternative Access Register™
Record:
alternative route;
availability;
accessibility;
delay;
cost;
suitability.
80. Independence Restoration Register™
Record:
dependency;
intervention;
alternative created;
autonomy impact;
current status.
81. SAFECHAIN™ Dependency Risk Dashboard™
Monitor:
DR3–DR5 dependency;
DP3–DP5 power imbalance;
MID3–MID5 multi-system dependency;
no-alternative cases;
remedy dependency;
evidence dependency;
lock-in effects;
challenge suppression;
exit barriers;
dependency duration.
82. Dependency Stress Test™
Scenario A — Service Fails Tomorrow
What realistic alternative exists?
Scenario B — Person Complains
Can challenge occur without jeopardising access?
Scenario C — Transfer Requested
Can support or information move with the person?
Scenario D — Delay
Does waiting increase dependency?
Scenario E — Evidence Needed
Can the person access records necessary to challenge?
Scenario F — Multiple Institutions
Does one dependency intensify another?
Scenario G — Service Ends
Does independence remain?
83. Dependency Reality Test™
Ask:
How much practical choice would remain if the institution stopped cooperating?
84. Alternative Reality Test™
Ask:
Are the alternatives real, or merely theoretical?
85. Exit Reality Test™
Ask:
Can the person leave without losing something essential?
86. Challenge Reality Test™
Ask:
Can the person challenge the institution while remaining secure in their access to essential services or rights?
87. Institutional Power Counterfactual™
Ask:
Would the institution's decision carry the same practical power if meaningful alternatives existed?
88. Dependency-to-Safeguarding Trigger™
Enhanced review should be considered where:
High Essentiality + Low Alternatives + High Gatekeeping Power + Serious Exit Cost
coexist.
89. Dependency Risk Classification Gate™
Before classifying dependency assess:
✓ essentiality
✓ alternatives
✓ accessibility
✓ gatekeeping power
✓ information control
✓ remedy access
✓ exit cost
✓ challenge safety
✓ duration
✓ cumulative vulnerability
90. Dependency Safeguard Gate™
Where material dependency exists verify:
✓ named owner
✓ independent challenge route
✓ information access
✓ alternative access considered
✓ exit consequences assessed
✓ reasonable portability available
✓ vulnerability monitored
91. Independence Restoration Gate™
Before closure verify:
✓ dependency reduced
✓ alternatives improved
✓ information access restored
✓ challenge rights protected
✓ exit barriers reduced
✓ residual dependency identified
✓ future review assigned
92. False-Positive Safeguard™
Not all institutional dependency is inappropriate.
Some dependency is unavoidable where institutions legitimately provide:
specialist healthcare;
statutory services;
regulated financial access;
judicial determination;
emergency safeguarding.
The issue is whether dependency is:
necessary;
proportionate;
transparent;
challengeable;
time-limited where possible;
safeguarded against misuse.
93. Necessary Dependency Standard™
Ask:
Is the level of dependency necessary to deliver the legitimate institutional function?
94. Proportional Dependency Test™
Ask:
Could the same institutional purpose be achieved with less dependency?
95. Dependency Minimisation Principle™
Where dependency cannot be eliminated, institutions should minimise its scope, duration and consequences.
96. No-Dependency-Equals-Abuse Principle™
Institutional dependency does not itself establish abuse, misconduct or illegality.
97. No-Theoretical-Alternative Principle™
An alternative is not meaningful if it is financially, geographically, procedurally or practically inaccessible.
98. No-Consent-by-Participation Principle™
Continued participation in a service does not prove that dependency conditions are freely accepted where exit carries disproportionate consequences.
99. ESCALATION-001™ Integration
High dependency and exit risk may lower escalation thresholds where institutional failure could produce serious harm.
100. CONTINUITY-001™ Integration
Dependency may intensify where staff changes or transfers cause loss of access, history or ownership.
101. CUMULATIVEHARM-001™ Integration
Institutional dependency may contribute to cumulative harm across time and domains.
102. RECURRINGFAILURE-001™ Integration
Repeated service failure can transform ordinary reliance into entrenched dependency risk.
103. INSTITUTIONALCLEANSLATE-001™ Integration
A context reset may cause the institution to underestimate the duration or severity of dependency.
104. CONTROLAMPLIFICATION-001™ Integration
Institutional control points may amplify existing dependency or coercive power.
105. RESPONSIBILITYDISPLACEMENT-001™ Integration
Dependency should not result in the affected person being blamed for barriers created by the institution.
106. FEEDBACK-001™ Integration
Reports of dependency barriers should inform service redesign.
107. DESIGN-001™ Integration
Dependency minimisation should be embedded through Safeguard-by-Design.
108. SYSTEMCHECK-001™ Integration
Institutional systems should be stress-tested to determine what happens when:
access fails;
staff change;
service stops;
records are delayed;
appeal is made;
a person requests transfer.
109. FLOW-001™ Integration
Process flow should identify institutional control points where dependency is created or intensified.
110. INTERFACE-001™ Integration
Cross-system boundaries should support portability and prevent people becoming trapped between institutions.
111. DEPENDENCYRISK-001™ Integrity Test
The institution should be able to demonstrate that:
Institutional Dependency Creation™ is recognised.
Service-Induced Vulnerability™ is assessed.
Exit Risk™ is assessed.
Institutional control points are mapped.
Gatekeeping power is assessed.
Single-route dependency is identified.
alternative scarcity is assessed.
institutional monopoly risk is assessed.
DR1–DR5 dependency can be classified.
Service-Induced Vulnerability Test™ operates.
dependency amplification is assessed.
delay-induced dependency is recognised.
procedural dependency is assessed.
information dependency is assessed.
evidence dependency is assessed.
remedy dependency is assessed.
internal-remedy monopoly is identified.
challenge dependency is assessed.
retaliatory dependency risk is considered.
silence-by-dependency is assessed.
exit consequences are mapped.
institutional exit barriers are identified.
lock-in effects are assessed.
forced continuation risk is recognised.
choice integrity is assessed.
Institutional Manufactured Choice™ is considered.
Dependency Power Index™ is assessed.
DP1–DP5 dependency power can be classified.
institutional vulnerability creation is assessed.
vulnerability preservation is assessed.
Dependency Cascades™ are mapped.
cross-system dependency is assessed.
dependency compounding is identified.
MID1–MID5 multi-institution dependency can be classified.
Dependency Chronology™ is maintained.
dependency duration is assessed.
dependency persistence is reviewed.
dependency recovery deficit is identified.
independence restoration is assessed.
Independence-by-Design™ operates.
Dependency Prevention Principle™ applies.
Dependency Safeguard Architecture™ exists.
Control Point Register™ exists.
Dependency Risk Register™ exists.
Exit Barrier Register™ exists.
Alternative Access Register™ exists.
Independence Restoration Register™ exists.
Dependency Risk Dashboard™ operates.
Dependency Stress Test™ operates.
Dependency Reality Test™ operates.
Alternative Reality Test™ operates.
Exit Reality Test™ operates.
Challenge Reality Test™ operates.
Institutional Power Counterfactual™ operates.
dependency can trigger safeguarding escalation.
Dependency Risk Classification Gate™ operates.
Dependency Safeguard Gate™ operates.
Independence Restoration Gate™ operates.
false-positive safeguards operate.
necessary dependency is distinguished from avoidable dependency.
proportional dependency is tested.
Dependency Minimisation Principle™ operates.
theoretical alternatives are not treated as meaningful.
participation is not treated as proof of free consent.
cross-framework dependencies are recognised.
And ultimately:
Can the institution demonstrate that its service enables the person to exercise rights, access support and obtain remedy without making that person more dependent upon the institution than the legitimate purpose of the service requires?
112. Framework Outcomes
Implementation establishes:
✓ Institutional Dependency Creation™
✓ Service-Induced Vulnerability™
✓ Exit Risk™
✓ SAFECHAIN™ Institutional Dependency Architecture™
✓ Institutional Control Point™
✓ Gatekeeping Power™
✓ Single-Route Dependency™
✓ Alternative Scarcity™
✓ Institutional Monopoly Risk™
✓ DR1–DR5 Dependency Severity Classification™
✓ Dependency Amplification™
✓ Delay-Induced Dependency™
✓ Procedural Dependency™
✓ Information Dependency™
✓ Evidence Dependency™
✓ Remedy Dependency™
✓ Internal-Remedy Monopoly™
✓ Challenge Dependency™
✓ Retaliatory Dependency Risk™
✓ Silence-by-Dependency™
✓ Exit-Risk Architecture™
✓ Institutional Exit Barrier™
✓ Lock-In Effect™
✓ Forced Continuation Risk™
✓ Institutional Manufactured Choice™
✓ Dependency Power Index™
✓ DP1–DP5 Dependency Power Classification™
✓ Institutional Vulnerability Creation™
✓ Vulnerability Preservation™
✓ Dependency Cascade™
✓ Cross-System Dependency™
✓ Dependency Compounding™
✓ MID1–MID5 Multi-Institution Dependency Classification™
✓ Dependency Chronology™
✓ Dependency Duration™
✓ Dependency Recovery Deficit™
✓ Institutional Independence Restoration™
✓ Independence-by-Design™
✓ Dependency Prevention Principle™
✓ SAFECHAIN™ Dependency Safeguard Architecture™
✓ Control Point Register™
✓ Dependency Risk Register™
✓ Exit Barrier Register™
✓ Alternative Access Register™
✓ Independence Restoration Register™
✓ SAFECHAIN™ Dependency Risk Dashboard™
✓ Dependency Stress Test™
✓ Dependency Reality Test™
✓ Alternative Reality Test™
✓ Exit Reality Test™
✓ Challenge Reality Test™
✓ Institutional Power Counterfactual™
✓ Dependency Risk Classification Gate™
✓ Dependency Safeguard Gate™
✓ Independence Restoration Gate™
✓ Necessary Dependency Standard™
✓ Dependency Minimisation Principle™
✓ DEPENDENCYRISK-001™ Integrity Test™
113. Framework Statement
Dependency becomes a governance risk when access to something essential—housing, money, healthcare, evidence, safeguarding, legal participation or remedy—depends so heavily upon one institutional route that the person cannot safely challenge, leave or obtain an alternative. The service may technically remain available while the person's practical freedom narrows around it. Delay can remove alternatives. Information control can prevent challenge. Internal complaint routes can make the institution both decision-maker and gatekeeper of remedy. Continued participation can then appear voluntary even when exit carries disproportionate loss. DEPENDENCYRISK-001™ establishes the SAFECHAIN™ architecture for identifying those conditions, reducing avoidable gatekeeping, protecting challenge rights, increasing real alternatives and ensuring that institutions provide essential support without unnecessarily converting need into institutional dependency.
114. Copyright & Intellectual Property Notice
© 2026 Samantha Avril-Andreassen. All Rights Reserved.
DEPENDENCYRISK-001™ — The SAFECHAIN™ Institutional Dependency Creation, Service-Induced Vulnerability & Exit-Risk Framework™ is an original institutional-governance, safeguarding, dependency-risk, service-design, vulnerability and systems-reform framework developed and authored by Samantha Avril-Andreassen, LLB (Hons), LLM, LPC, FRSA, Founder of SAFECHAIN™.
DEPENDENCYRISK-001™ forms part of the SAFECHAIN™ Justice & Institutional Integrity Series™ and wider SAFECHAIN™ Governance Architecture™.
The original expression, selection, arrangement and combination of its architecture, terminology, tests, classifications, registers, matrices, safeguards, dependency measures and verification gates constitute proprietary intellectual property to the extent protected by applicable law.
Protected elements include, where original to this framework, Institutional Dependency Creation™, Service-Induced Vulnerability™, Exit Risk™, SAFECHAIN™ Institutional Dependency Architecture™, Institutional Control Point™, Gatekeeping Power™, Single-Route Dependency™, Alternative Scarcity™, Institutional Monopoly Risk™, Dependency Amplification™, Delay-Induced Dependency™, Procedural Dependency™, Information Dependency™, Evidence Dependency™, Remedy Dependency™, Internal-Remedy Monopoly™, Challenge Dependency™, Retaliatory Dependency Risk™, Silence-by-Dependency™, Exit-Risk Architecture™, Institutional Exit Barrier™, Lock-In Effect™, Forced Continuation Risk™, Institutional Manufactured Choice™, Dependency Power Index™, Institutional Vulnerability Creation™, Vulnerability Preservation™, Dependency Cascade™, Cross-System Dependency™, Dependency Compounding™, Dependency Chronology™, Dependency Recovery Deficit™, Institutional Independence Restoration™, Independence-by-Design™, Dependency Prevention Principle™, SAFECHAIN™ Dependency Safeguard Architecture™, Control Point Register™, Dependency Risk Register™, Exit Barrier Register™, Alternative Access Register™, Independence Restoration Register™, SAFECHAIN™ Dependency Risk Dashboard™, Dependency Reality Test™, Institutional Power Counterfactual™, Dependency Risk Classification Gate™, Dependency Safeguard Gate™, Independence Restoration Gate™, Dependency Minimisation Principle™ and DEPENDENCYRISK-001™ Integrity Test™, together with associated implementation materials.
No part of this framework may be reproduced, republished, substantially adapted, distributed, commercially exploited or incorporated into another proprietary governance, safeguarding, service-design, dependency-risk, training, certification, consultancy, artificial-intelligence, analytics or software system without prior written permission from the applicable rights holder, except as permitted by applicable law.
Publication or citation does not transfer ownership of SAFECHAIN™ intellectual property or confer authority to issue SAFECHAIN™ assessments, classifications, certifications, accreditations or verification findings.
References to generally established concepts concerning dependency, vulnerability, access to services, safeguarding, monopoly, institutional power, complaints, review and service design do not constitute claims of ownership over those underlying concepts. Proprietary claims relate to original SAFECHAIN™ expression, architecture, terminology, arrangement and methodology to the extent protected by applicable law.
DEPENDENCYRISK-001™ does not establish that institutional dependency is inherently abusive or unlawful. Some dependency is unavoidable in the delivery of essential public, regulated and specialist services. Application must therefore remain evidence-based, proportionate and attentive to necessity, competing duties, lawful restrictions and realistic alternatives.
Author and Framework Developer:
Samantha Avril-Andreassen, LLB (Hons), LLM, LPC, FRSA
Founder — SAFECHAIN™
Framework Reference: DEPENDENCYRISK-001™
Framework Series: SAFECHAIN™ Justice & Institutional Integrity Series™
Parent Architecture: SAFECHAIN™ Governance Architecture™
Version: 1.0
Year: 2026
© 2026 Samantha Avril-Andreassen. All Rights Reserved.