SAFECHAIN™ Architecture Dependency Map™
Mapping the Interrelationship of the SAFECHAIN™ Research, Governance and Infrastructure Programme
Series: Architecture Governance Series™
Document Reference: AGS-001
Author: Samantha Avril-Andreassen FRSA
Organisation: SAFECHAINN Ltd
Executive Summary
As the SAFECHAIN™ programme has expanded, individual papers have increasingly become components of a larger architecture.
What began as a series of independent analyses has evolved into a connected ecosystem of governance frameworks, verification systems, safeguarding architectures and implementation models.
This evolution creates a new challenge.
As architectures expand, relationships between papers become more difficult to visualise.
Without explicit mapping, risks emerge:
duplication;
terminology drift;
framework overlap;
implementation ambiguity;
governance fragmentation.
The purpose of the SAFECHAIN™ Architecture Dependency Map™ is therefore to establish a formal architecture lineage model.
This document identifies:
architecture layers;
dependency relationships;
implementation hierarchy;
governance hierarchy;
evidence hierarchy;
publication hierarchy.
The objective is to ensure that every SAFECHAIN™ publication can be traced to its originating concepts and linked to its dependent frameworks.
Section 1
SAFECHAIN™ Architecture Hierarchy
The SAFECHAIN™ programme currently operates through five principal layers.
Layer 1
Applied Analysis Series™ (AAS)
Purpose:
Problem identification.
Function:
Diagnostic architecture.
Core Question:
Why do systems fail?
Examples:
Participation Integrity™
Accountability Gap™
Institutional Recognition Failure™
Architecture of Preventable Harm™
Output:
Problem definition.
Layer 2
External Evidence Response Series™ (EERS)
Purpose:
Evidence integration.
Function:
External validation architecture.
Core Question:
Do national evidence sources identify the same failures?
Examples:
Known To The System™
The Predictable Tragedy™
Health Continuity Failure™
Safeguarding Without Interoperability™
Output:
Evidence validation.
Layer 3
National Vulnerability Verification Infrastructure™ (NVI)
Purpose:
Infrastructure design.
Function:
Verification architecture.
Core Question:
How should systems be redesigned?
Examples:
Verified Vulnerability Credentials™
Financial Vulnerability Verification™
Government Silo Architecture™
Property Interest Verification Framework™
Output:
Infrastructure models.
Layer 4
National Operating Model™ (NOM)
Purpose:
Operational governance.
Function:
Implementation architecture.
Core Question:
Who operates the infrastructure?
Examples:
Trust Authority Framework™
Accreditation Framework™
Governance Council™
Audit & Assurance Framework™
Output:
Operating model.
Layer 5
The Directive™
Purpose:
Strategic interpretation.
Function:
Public governance commentary.
Core Question:
Why does this architecture matter?
Examples:
The Continuity Crisis™
SAFECHAIN™ Is Not A Database™
Why Vulnerability Is Not A Sector™
Output:
Strategic narrative.
Section 2
Architecture Dependency Structure
SAFECHAIN™ follows a sequential dependency model.
AAS
↓
EERS
↓
NVI
↓
NOM
↓
Directive™
This means:
Applied Analysis identifies failures.
External Evidence validates failures.
Infrastructure papers propose solutions.
Operating Models govern solutions.
Directive papers explain solutions.
No architecture should bypass this hierarchy without explicit justification.
Section 3
Major Architecture Clusters
The register currently reveals five dominant architecture clusters.
Cluster 1
Participation Architecture™
Primary Source:
AAS
Dependencies:
Participation Integrity™
Effective Participation™
Equality of Arms™
Linked Papers:
FPR Part 3A Analysis
Equal Treatment Bench Book Response
NVI Links:
Verified Vulnerability Credentials™
NOM Links:
Accreditation Framework™
Cluster 2
Safeguarding Continuity Architecture™
Primary Sources:
EERS
Dependencies:
Known To The System™
High-Risk Visibility Failure™
Predictable Tragedy™
Safeguarding Without Interoperability™
NVI Links:
National Vulnerability Verification Infrastructure™
NOM Links:
Governance Council™
Cluster 3
Financial Vulnerability Architecture™
Primary Sources:
NVI
Dependencies:
Financial Vulnerability Verification™
Credit Harm Verification Framework™
Trusted Income Verification™
NOM Links:
Audit & Assurance Framework™
Cluster 4
Government Interoperability Architecture™
Primary Sources:
NVI
Dependencies:
Government Silo Architecture™
EERS Links:
NHS Integrated Care Systems™
Multi-Agency Safeguarding Arrangements™
NOM Links:
National Operating Model™
Cluster 5
National Infrastructure Architecture™
Primary Sources:
NVI + NOM
Dependencies:
Verification Layer™
Trust Authority Framework™
Accreditation Framework™
Audit & Assurance Framework™
Purpose:
National implementation.
Section 4
Architecture Dependency Matrix
The following hierarchy now exists:
AAS → EERS
Problem Validation
EERS → NVI
Infrastructure Requirement
NVI → NOM
Governance Requirement
NOM → Directive
Strategic Communication
This structure now forms the official SAFECHAIN™ dependency model.
Section 5
Register Governance Rule
From publication version 1.0 onwards:
Every new SAFECHAIN™ publication must identify:
Parent Architecture
Dependent Architectures
Register Links
Implementation Links
Governance Links
No publication should exist in isolation.
Every paper must form part of the wider architecture.
Conclusion
The SAFECHAIN™ Architecture Dependency Map™ establishes the first formal lineage model for the programme.
The document confirms that SAFECHAIN™ is no longer a collection of individual papers.
It is a connected governance and infrastructure ecosystem.
Future publications must therefore be evaluated not only on their individual merit but on their contribution to the wider architecture.
The purpose of this document is to ensure that the architecture remains coherent, scalable, auditable and implementation-ready as development continues.
COPYRIGHT NOTICE
© 2026 Samantha Avril-Andreassen. All rights reserved.
SAFECHAINN Ltd (Company No. 12038453).
SAFECHAIN™, SAFECHAIN™ Architecture Dependency Map™, Architecture Governance Series™, AGS-001™, Participation Architecture™, Safeguarding Continuity Architecture™, Financial Vulnerability Architecture™, Government Interoperability Architecture™, National Infrastructure Architecture™, National Vulnerability Verification Infrastructure™, Verified Vulnerability Credentials™, Government Silo Architecture™, Financial Vulnerability Verification™, Credit Harm Verification Framework™, Trusted Income Verification™, Trust Authority Framework™, Accreditation Framework™, Governance Council™, Audit & Assurance Framework™, Participation Integrity™, Accountability Gap™, Institutional Recognition Failure™, Known To The System™, The Predictable Tragedy™, Health Continuity Failure™, Safeguarding Without Interoperability™, The Continuity Crisis™, Why Vulnerability Is Not A Sector™, SAFECHAIN™ Is Not A Database™ and all associated methodologies, frameworks, governance models, standards, operating models, interoperability architectures, safeguarding systems, verification infrastructures, credential systems, pilot architectures, implementation frameworks, policy frameworks, training methodologies, audit systems, intelligence models, analytics models, dependency models, architecture maps and intellectual constructs are proprietary intellectual property authored and developed by Samantha Avril-Andreassen.
No reproduction, implementation, adaptation, deployment, AI training, machine learning ingestion, commercialisation, derivative development, institutional adoption, regulatory implementation, governmental implementation, software development, systems development, framework replication, architecture replication or operational deployment may occur without prior written permission from Samantha Avril-Andreassen and SAFECHAINN Ltd.
The SAFECHAIN™ Master Publication Register™ remains the sole authoritative source of publication status, architecture lineage, governance authority, terminology control, implementation hierarchy and intellectual property provenance.