APPLIED ANALYSIS SERIES — AAS-012
THE DIRECTIVE™ — APPLIED ANALYSIS SERIES — AAS-012
Institutional Capture™: Applying Paper 32 — The Power Paradox™
A SAFECHAIN™ Synthesis of AAS-001 to AAS-011, Examining the Structural Conditions Under Which Organisations Shift From Protecting the Public to Protecting Themselves
Reference: SAFECHAIN/AAS/2026/012
Author: Samantha Avril-Andreassen FRSA
Organisation: SAFECHAINN Ltd (Company No. 12038453)
Abstract
This paper is the first applied analysis of Paper 32 of the SAFECHAIN™ Foundational Architecture Index™, The Power Paradox™, which examines how institutions created to protect the public may, over time, become focused on managing institutional exposure, organisational stability, procedural defensibility, and reputational risk. Paper 32 was first distinguished from Paper 6 (The Institutional Failure Taxonomy™) in AAS-007 of this series, and reserved there for a future piece on institutional self-protection responses. This is that piece.
This paper refers to the operational manifestation of Paper 32 as Institutional Capture™: a condition in which institutional priorities gradually shift from public protection toward institutional self-preservation, without requiring bad faith, misconduct, or intentional wrongdoing by any individual.
This is the third synthesis paper in this series, following AAS-010 (why implementation fails) and AAS-011 (why accountability becomes difficult to locate). AAS-010 and AAS-011 each found a recurring pattern across AAS-001 to AAS-009: a problem is recognised, a response is correctly scoped, and yet the broader problem persists, with no single actor identifiable as responsible for the persistence. This paper asks the next question in that sequence: what structural incentives might make persistence of this kind more likely, even where every individual actor is acting in good faith?
Using Paper 32 (The Power Paradox™) as its primary framework, supported by Paper 22 (The Accountability Paradox™), Paper 23 (The Implementation Paradox™), and Paper 33 (The Responsibility Paradox™), and applying Paper 6 (The Institutional Failure Taxonomy™) for the first time in this series as a five-category taxonomy of capture mechanisms, this paper examines four findings from AAS-001, AAS-007, AAS-010 and AAS-011 through the lens of Institutional Capture™.
This paper does not suggest bad faith, misconduct, or intentional wrongdoing by institutions. The analysis concerns governance dynamics, organisational incentives, and structural behaviour, in the same register AAS-011 examined directly as this series' method.
Keywords: Institutional Capture™, The Power Paradox™, The Institutional Failure Taxonomy™, Accountability, Implementation, Governance, SAFECHAIN™, The Directive™
A Note on This Paper's Role and Framework
This is the third paper in a sequence that began with AAS-010 and AAS-011, and its relationship to both is direct. AAS-010 found that the relationships between correctly-scoped responses to recognised problems are nobody's particular concern. AAS-011 found that, for the structural gaps AAS-001 to AAS-009 each identified, a specific point of responsibility is frequently not locatable, even where the gap itself can be precisely described. Both papers stopped short of asking why this pattern recurs as consistently as it does. This paper takes up that question, using Paper 32 — reserved for this purpose since AAS-007 — as its primary framework.
On Paper 6: AAS-006, AAS-007 and AAS-010 each referenced Paper 6 (The Institutional Failure Taxonomy™) without applying it, and AAS-011's scope note recorded that a fourth gestural reference should be avoided in favour of either proper application or omission. This paper applies Paper 6 for the first time, as a five-category taxonomy of capture mechanisms — Reputational, Procedural, Compliance, Resource, and Defensive Capture — set out in Section 3. This is offered as Paper 6's first substantive application in the series, addressing the gap AAS-011 identified.
On grounding: as the third synthesis paper, this paper does not use hypothetical examples. Section 2 grounds Institutional Capture™ in four specific findings — from AAS-001, AAS-007, AAS-010 and AAS-011 — asking, for each, what structural incentive might make the pattern found there persist. The five capture types in Section 3 are then applied to these same four findings, rather than to new hypothetical scenarios.
1. Introduction: A Question AAS-010 and AAS-011 Did Not Ask
AAS-010 found that institutions can recognise a problem, develop a response correctly scoped to that problem, and comply with it, while the broader problem persists because the relationships between responses were never anyone's responsibility. AAS-011 found that this is not only true of relationships between responses: for the individual structural gaps AAS-001 to AAS-009 each identified, the question of whose responsibility a gap is frequently has no ready answer, even where the gap itself is precisely describable.
Neither paper asked why this pattern — recognition without resolution, describable gaps without locatable responsibility — recurs as consistently as it does. One possible answer is that it is simply difficult: complex systems are, as Paper 22 states, systems in which accountability becomes harder to locate as complexity increases, and this may be sufficient explanation on its own. This paper examines a second, complementary possibility: that some of the persistence AAS-010 and AAS-011 found may be explained not only by complexity making resolution difficult, but by institutional incentives making the absence of resolution, in some respects, easier to sustain than its presence would be — not through any institution's intent, but as a structural property of how institutions evaluate their own performance.
2. Four Findings, Revisited
The table below sets out the four findings this paper grounds itself in, each drawn directly from an earlier paper in this series.
Paper
Finding
Known safeguarding information (coercive control) not fully surviving the move from Cafcass enquiries to the family court via the C1A form
A risk grading recognised at MARAC stage, weakened or lost by the time it reaches a safeguarding letter
Implementation recognised as necessary (per the Harm Panel, 2020) but operational change incomplete five years later
Accountability for a structural gap recognised as desirable, but a specific point of responsibility not locatable
For each of these four findings, AAS-001, AAS-007, AAS-010 and AAS-011 each, independently, declined to attribute the finding to any actor's failure — AAS-001 examined a form's design; AAS-007 examined a statistical category's absence; AAS-010 examined the scope of individual reforms; AAS-011 examined the structure of responsibility itself. This paper's question is not whether any of these four findings should instead have been attributed to an actor's failure — AAS-011 Section 5 addressed why that framing would be the wrong one. This paper's question is: for each of these four findings, is there a way in which the institutions involved might, in practice, evaluate their own performance such that the finding's persistence is not registered as a performance problem at all?
3. A Taxonomy of Capture Mechanisms (Paper 6, Applied)
Paper 6, The Institutional Failure Taxonomy™, provides a framework for categorising failure modes. This paper applies it here, for the first time in this series, as a taxonomy of five capture mechanisms — ways in which an institution's evaluation of its own performance can become detached from the public purpose that performance is meant to serve, while every individual step in the process remains procedurally correct.
Capture Type
Description
Reputational Capture
A process that exists to establish facts is evaluated, in part, by how its findings will be received externally, alongside whether the findings are accurate
Procedural Capture
Compliance with a process becomes the measure of whether the process worked, independent of the outcome the process was designed to produce
Compliance Capture
A requirement is satisfied in a form that can be evidenced (a form completed, a box ticked, a meeting held) without a corresponding mechanism for evidencing the requirement's purpose was met
Resource Capture
A function that would address a structural gap is not resourced, while functions that demonstrate the institution is managing its own risk are resourced
Defensive Capture
A response to an identified problem is framed, in part, around how the response itself could be characterised if scrutinised, alongside whether the response addresses the problem
Applied to Section 2's table: AAS-001's C1A form may illustrate Procedural Capture — the form's completion, not the coercive control field's absence, is what is measured. AAS-007's statistical category may illustrate Resource Capture — recording strangulation separately within crime statistics would require a resourcing decision that recording it within 'Assault with injury' does not. AAS-010's bounded reforms may illustrate Compliance Capture — the Express FR Pilot's success is measured by its own terms (cases processed under PD36ZH), not by whether procedural burden, AAS-009's broader subject, has changed. AAS-011's unlocatable responsibility may illustrate a combination of Reputational and Defensive Capture — where responsibility for a gap is genuinely hard to locate, as AAS-011 found, an institution's account of its own role in that gap may, without anyone intending this, tend toward the account that is least exposing to give, among several accounts that might all be equally accurate.
This paper does not claim that any of these four applications is the only, or even the primary, explanation for the finding it is applied to. AAS-010 and AAS-011 each offered their own explanations — implementation scope, and the structure of responsibility, respectively — and this paper's applications are offered as additional, complementary readings, not replacements for those explanations.
4. Mission to Maintenance: The Shift, Not the State
Institutional Capture™, as this paper uses Paper 32, describes a shift rather than a state. An institution is not 'captured' or 'not captured' as a binary; the five capture types in Section 3 describe directions in which an institution's evaluation of its own performance can move, by degrees, without any single decision marking the transition.
The shift can be described in general terms: questions of the form 'are we achieving the outcome this institution exists to achieve' become, in practice though rarely in stated policy, supplemented or in places substituted by questions of the form 'have we followed the procedure,' 'have we reduced our exposure,' and 'can this be defended if scrutinised.' None of these latter questions is illegitimate — procedure, risk management, and defensibility all matter, and an institution that ignored them entirely would not thereby better serve its public purpose. The shift this paper describes is one of relative weight: when the second set of questions becomes the primary measure by which an institution evaluates whether it is succeeding, Paper 32 describes the institution as exhibiting Institutional Capture™, regardless of whether any individual within it intends this or would, if asked directly, endorse it as a description of their own priorities.
5. The Accountability Paradox™, Revisited: Capture as a Stabiliser
AAS-011 found, via Paper 22, that as systems become more complex, accountability becomes more difficult to locate — a property of complexity itself, independent of intent. This paper's contribution to that finding is to note a feedback relationship: if accountability is difficult to locate (AAS-011's finding), and an institution's performance is evaluated partly through Section 3's capture mechanisms — particularly Procedural and Compliance Capture, where demonstrating the process was followed substitutes, in practice, for demonstrating the outcome was achieved — then the difficulty of locating accountability may not register, within the institution's own evaluation of itself, as a problem requiring resolution. The institution can correctly report that its processes were followed, because they were; the separate question of whether the outcome those processes existed to produce was achieved is not the question Procedural or Compliance Capture asks.
This is not a claim that institutions prefer unaccountability, or that unaccountability is sought. It is a claim that, where Section 3's capture mechanisms are present, the absence of locatable accountability and the institution's own measure of its success may not be in tension — and where two things are not in tension, there is, structurally, less pressure for either to change. Paper 33, The Responsibility Paradox™, describes the resulting distribution of partial responsibility across multiple actors; this paper's addition is that this distribution, once established, may be relatively stable — not because anyone defends it, but because no part of it, examined through Section 3's mechanisms, presents as a problem from within.
6. The Implementation Paradox™, Revisited: Why Scope Stays Bounded
AAS-010 found, via Paper 23, that reforms are correctly scoped to the problem as understood at the time of their design, and that the relationships between reforms are nobody's particular concern. This paper's contribution is to note that Compliance Capture, as defined in Section 3, gives a reform's original scope a specific kind of stability: a reform's success is measured against its own scope (did the Express FR Pilot reduce burden for the cases PD36ZH applies to?), and an answer to that question — even a positive one — does not, on its own terms, generate a question about cases or burdens outside that scope.
This is not an argument that reforms should be scoped more broadly; AAS-009 was explicit that broader scope can itself become part of the cumulative burden problem. It is an observation that, once a reform is scoped and judged successful within that scope, the institutional incentive to revisit the scope itself — to ask 'was this the right boundary' rather than 'did we meet the boundary we set' — may be weaker than the incentive that justified the reform in the first place, for reasons Section 3's Compliance Capture describes.
7. What Might Follow
Consistent with AAS-010 and AAS-011's proposals, the suggestions below do not propose detecting or correcting 'institutional capture' as a named condition — doing so would risk becoming exactly the kind of compliance-measurable intervention Section 6 describes, evaluated by whether the detection process was followed rather than by its effect.
• Whether, when a reform's success is reported (as the Express FR Pilot's will be, at the end of its pilot period in April 2026), the report could include, alongside whether the reform met its own scope, a brief note of what AAS-009's 'multiplication effect' or similar cumulative questions outside that scope remain — not as a criticism of the reform, but as a record that the boundary was a boundary, for whoever next considers it
• Whether the five capture types in Section 3 could be used, by an institution reviewing its own processes, as a set of questions to ask of a process that has been operating successfully by its own measures for some time — not 'is this process captured' but 'if it were, which of these five forms would it most likely take, and would our current reporting show us that'
• Whether AAS-001 through AAS-011's findings, several of which Section 2 revisited here, could be periodically re-examined specifically for whether any of Section 3's five capture types newly applies — given that, as Section 4 noted, capture is a shift rather than a state, and a finding accurately described as not exhibiting a given capture type at the time of writing could come to exhibit it later
8. Conclusion: A Structural Property, Not a Verdict
This paper has applied Paper 32, The Power Paradox™, for the first time in this series, to four findings AAS-001, AAS-007, AAS-010 and AAS-011 each established independently. In each case, this paper has suggested a way in which the finding's persistence might be, in part, structurally unsurprising — not because any institution involved sought that persistence, but because the mechanisms by which institutions typically evaluate their own success may not, in each of these four cases, register the persistence as a failure of that success.
This is offered as a structural property, not a verdict on any institution named or implied across AAS-001 to AAS-011. AAS-011 Section 5 examined, as this series' own method, the discipline of describing structures rather than attributing blame; this paper has attempted to extend that discipline to the question of why structures persist, without converting the answer into an accusation. Paper 32 was reserved, since AAS-007, for a piece that could do this. Whether it has done so is, appropriately, a question this paper's own argument suggests should be asked again later — not answered once, here, and considered closed.
Reading This Alongside the Architecture
This paper forms part of The Directive™ Applied Analysis Series and should be read alongside:
• Paper 32 — The Power Paradox™ (primary; first application in this series)
• Paper 6 — The Institutional Failure Taxonomy™ (first substantive application in this series, as the five-part taxonomy in Section 3)
• Paper 22 — The Accountability Paradox™
• Paper 23 — The Implementation Paradox™
• Paper 33 — The Responsibility Paradox™
This paper's primary references are AAS-001, AAS-007, AAS-010 and AAS-011 of this series, particularly the four findings tabulated in Section 2.
SAFECHAIN™ welcomes discussion with the institutions named across AAS-001 to AAS-011 on the questions raised in Section 7.
References
AAS-001 — Two Reports, One Chain: Reading the Domestic Abuse Commissioner's Findings Alongside Scratching the Surface.
AAS-007 — Non-Fatal Strangulation and the Failure of Risk Transmission.
AAS-009 — The Administrative Weaponisation of Procedure.
AAS-010 — The Implementation Paradox™: When Knowing Is Not the Same as Doing.
AAS-011 — The Accountability Gap™: How Responsibility Becomes Difficult to Locate in Complex Systems.
© 2026 Samantha Avril-Andreassen. All rights reserved. SAFECHAINN Ltd (Company No. 12038453).
Version 1.0
Reference: SAFECHAIN/AAS/2026/012
Copyright & Intellectual Property Notice
© 2026 Samantha Avril-Andreassen. All rights reserved.
SAFECHAIN™, SAFECHAINN Ltd, The Directive™, Participation Integrity™, Passport of Erasure™, Shadow Ledger™, Coercive Debt Lifecycle™, Legacy Harm Architecture™, Institutional Failure Taxonomy™, Vulnerability Index™, Safeguarding Intelligence Model™, Seal of Integrity™, MØPIT™, SIP™, CPIT™, REBUILD™, COMPASS™, and all associated frameworks, methodologies, models, diagrams, terminology, research architecture, governance structures, assessment tools, training systems, and implementation mechanisms are proprietary intellectual property authored by Samantha Avril-Andreassen.
No part of this publication may be reproduced, copied, adapted, distributed, implemented, commercialised, taught, incorporated into training programmes, accreditation schemes, policy frameworks, software systems, artificial intelligence models, governance products, consultancy services, or derivative works without the prior written permission of the author.
The existence of this publication does not grant any licence to implement, replicate, modify, commercialise, or operationalise any SAFECHAIN™ intellectual property.
All rights reserved.