Framework Overview — Applicability Boundary Doctrine

Status: Framework overview (non-claim)

Introduction

The Applicability Boundary Doctrine is a conceptual framework for observing and documenting the limits of explanation in complex automated, AI-enabled and safety-critical systems, including systems operating in regulated or high-consequence environments.

This page provides a structural overview of the framework layers. It does not prescribe actions, assign responsibility, or replace regulatory investigation.

Conceptual Architecture

The framework is organised into the following layers:

Doctrine
  ↓
Terminology
  ↓
Architecture
  ↓
Diagnostic Framework
  ↓
Stakeholder Context

Each layer extends the conceptual vocabulary without modifying the canonical doctrine.

Layer 1 — Canonical Doctrine

The canonical doctrine defines the foundational concepts of applicability boundaries. It establishes the principle that systems may operate beyond the conditions that justify their operation, and that this condition is structurally distinct from component failure.

Canonical version: v1.4.3

• Doctrine — Canonical doctrine page.
• Citation — How to cite the doctrine.

Layer 2 — Terminology Anchor

The terminology layer defines the conceptual vocabulary used throughout the framework. Terms include Applicability Boundary, Operational Mode, Invalid Operational Mode, Behaviour Governance, and Applicability Architecture.

• Glossary — Complete terminology reference.
• Terminology Authority — Authority and scope of terminology.
• Terminology Applicability Reference — Applicability of terminology definitions.

Layer 3 — Conceptual Architecture

The architecture layer describes the structural relationships between applicability boundaries, operational modes, and system behaviour governance.

• Applicability Architecture — Conceptual architecture overview.
• Applicability Boundary — Definition — Formal definition of the applicability boundary concept.
• Applicability Architecture — Terminology — Terminology within the architecture.

Layer 4 — Diagnostic Framework

The diagnostic layer provides conceptual tools for analysing failure classes and incident interpretation without prescribing detection mechanisms or operational procedures.

• Applicability Failure Map — Structural failure classes.
• Annex — Failure Archetypes — Archetypal failure patterns.
• Applicability Incident Lens — Conceptual incident analysis framework.

Layer 5 — Stakeholder Perspectives

The stakeholder layer provides conceptual orientation for different audiences. These pages do not prescribe actions; they describe how applicability boundaries are relevant to each perspective.

• For Operators — Operational perspective.
• For Regulators — Regulatory perspective.
• For System Architects — Architectural perspective.
• For Engineers — Engineering perspective.
• For Auditors — Assurance perspective.
• For Investors — Investment risk perspective.
• For Insurers — Systemic risk perspective.

Conceptual Notes

The following notes provide additional conceptual orientation:

• Index Note — What this site is.
• Boundary Note — Conceptual boundary definitions.
• Evidence Note — Evidence interpretation framework.
• Scope Note — Scope limitations.
• Reading Order Note — Intended reading sequence.
• Cases Overview Note — Overview of illustrative cases.
• Interpretation Note — Applicability — Interpretation of applicability.

Non-Claim Integrity

All materials in this framework are intentionally non-claim. The framework describes structural properties of complex systems. It does not provide instructions, recommendations, or operational guidance.

End of Framework Overview