FrameworkThe Defensible AI Framework RegistrySheet 61

A registry makes a set of things addressable.

Canonical names, definitions and relationships for the governed production AI discipline.

← Defensible AI

§ 01Status

What this is.

The Defensible AI Framework Registry

Specification · Deposited. 10.5281/zenodo.22170112, version 1.0, CC BY 4.0. This is the concept DOI and it always resolves to the latest version.

The nine frameworks as one architecture The MESA Framework sits at the top as the diagnostic frame supplying four altitudes. Below it, five bands. The Regulatory Floor holds REG-08, the Sharia AI Compliance Framework, which enters as a second authority source. The Strategic Compass holds REG-07, the AI Governance Operating Model, which grants authority. Operational Machinery holds REG-06, the Five-Gate Deployment Model, as the lifecycle spine, fed from below by REG-02 model risk management, REG-04 vendor risk and REG-05 incident response. The Technical Substrate holds REG-03, data governance, which supplies the residency rule set. Beneath the altitudes sits the Boundary Invariant, an unmarked engineering-family law, carrying the BOE Declaration and REG-09, the Cross-Border Patterns, as its worked instance on the residency class. At the base is the evidence layer. Authority flows down the left side; evidence flows up the right. The nine frameworks as one architecture Nabeel Khan 2026 https://doi.org/10.5281/zenodo.22170112 https://doi.org/10.5281/zenodo.22170112 Copyright 2026 Nabeel A. Khan. Licensed CC BY 4.0. Nabeel Khan https://nabeelkhan.com/frameworks/registry THE NINE, AS ONE ARCHITECTURE REG-01 MESA Framework the diagnostic frame. It occupies no altitude AUTHORITY FLOWS DOWN EVIDENCE FLOWS UP ALTITUDE 1 · REGULATORY FLOOR REG-08 Sharia AI Compliance Framework a second binding authority source enters the same machinery as the first ALTITUDE 2 · STRATEGIC COMPASS REG-07 AI Governance Operating Model structure · decision rights · cadence grants the authority exercised below ALTITUDE 3 · OPERATIONAL MACHINERY REG-06 Five-Gate Deployment Model the lifecycle spine. G1 G2 G3 G4 G5 gate entry evidence REG-02 MESA MRM validation and approval REG-04 AVRF third-party AI diligence REG-05 AIRP reads every record below ALTITUDE 4 · TECHNICAL SUBSTRATE REG-03 AI Data Governance Framework supplies the residency rule set the patterns below architect around THE BOUNDARY INVARIANT · UNMARKED · ENGINEERING FAMILY a boundary is a clause the optimizer may not cross, and everything else is optimization BOE Declaration Boundary fixed · Optimizer freed · Evidence REG-09 Cross-Border Patterns worked instance · data residency class EVIDENCE LAYER BOE records · gate records · validations · attestations · reconstruction reports The Defensible AI Framework Registry v1.0 · Nabeel Khan · nabeelkhan.com/frameworks/registry · CC BY 4.0 · DOI 10.5281/zenodo.22170112
Figure 1. The nine as one architecture. Authority descends the altitudes; evidence ascends them.
§ 02What a registry is for

What a registry is for.

A registry is not a summary of the things it lists. A summary makes a long thing short. A registry makes a set of things addressable: it fixes their names so they can be cited, fixes their relationships so they can be sequenced, and fixes its own version so a claim made against it can be dated. The test is therefore not whether it describes its members accurately. It is whether a reader who has read none of the member documents can determine, from the registry alone, which framework applies to a given question, which other frameworks that one requires, what evidence it produces, who is accountable for it, and what would show it to be wrong.

Composition at the gates of the Five-Gate Deployment Model Five gates in sequence. Gate one, Data and Design, takes entry evidence from REG-03 classification and lineage and from REG-04 vendor clearance, and is accountable to the named data owner. Gate two, Validation, takes REG-02 steps one and two, accountable to the named validator. Gate three, Approval, takes REG-02 steps three and four and the closed dual validation of REG-08, accountable to the named executive. Gate four, Deployment, takes release authority from REG-07 and contractual controls from REG-04, accountable to the named platform owner. Gate five, Operation, takes armed triggers from REG-05 and live monitoring, accountable to the named head of the governance office. Each gate writes a gate passage record naming who approved, on what evidence, and when. Two reverse paths run backwards: rollback returns gate five to gate four with evidence preserved, and loop-back reopens gate two after an incident at gate five. Every gate passage record is an instance of the BOE Declaration. Composition at the gates of the Five-Gate Deployment Model Nabeel Khan 2026 https://doi.org/10.5281/zenodo.22170112 https://doi.org/10.5281/zenodo.22170112 Copyright 2026 Nabeel A. Khan. Licensed CC BY 4.0. Nabeel Khan https://nabeelkhan.com/frameworks/registry COMPOSITION AT THE GATES ENTRY EVIDENCE SUPPLIED BY REG-03 classification, lineage REG-04 clearance REG-02 steps 1 and 2 inventory, pre-validation REG-02 steps 3 and 4 REG-08 dual validation both tracks closed REG-07 release authority REG-04 contract terms REG-05 triggers armed monitoring live G1 Data and Design one named data owner G2 Validation one named validator G3 Approval one named executive G4 Deployment one named platform owner G5 Operation one named office head gate record who · on what · when gate record who · on what · when gate record who · on what · when gate record who · on what · when gate record who · on what · when ROLLBACK. G5 to G4, evidence preserved LOOP-BACK. an incident at G5 reopens G2 Every gate passage record is an instance of the BOE Declaration Boundary: the gate entry criteria. Optimizer: the deployment freedom granted on passage. Evidence: the record itself. This is what makes the governance and engineering families compose. The sequence and the entry criteria are normative. A gate passed without its entry evidence is not passed. The Defensible AI Framework Registry v1.0 · Nabeel Khan · nabeelkhan.com/frameworks/registry · CC BY 4.0 · DOI 10.5281/zenodo.22170112
Figure 2. How the frameworks compose at the gates of the deployment model.
§ 03The fifteen fields

The fifteen fields.

Three of the entry schema’s fifteen fields carry the weight. One accountable role, occupiable by one person. An evidence requirement that is a test rather than an aspiration. And a falsification condition, which is what separates a framework from a preference. An entry that marks no limitation is claiming a completeness no framework in this registry has.

The consolidation: twelve asserted marks become nine registry entries On the left, the twelve trademarks asserted on the copyright page of the Enterprise Playbook First Edition, with four defects marked: three names describing one subject, two instruments measuring one maturity, a name implying a technology stack, and no stated law connecting the twelve. On the right, nine registry entries REG-01 to REG-09 under one architecture, of which eight carry trademarks and one, the AI Governance Operating Model, is deliberately unmarked, plus two deliberately unmarked engineering-family names, the Boundary Invariant and the BOE Declaration. Four decisions produce the change: three frameworks consolidated into one, one instrument superseded, one framework renamed, and one repositioned. The consolidation: twelve asserted marks become nine registry entries Nabeel Khan 2026 https://doi.org/10.5281/zenodo.22170112 https://doi.org/10.5281/zenodo.22170112 Copyright 2026 Nabeel A. Khan. Licensed CC BY 4.0. Nabeel Khan https://nabeelkhan.com/frameworks/registry THE CONSOLIDATION BEFORE · TWELVE MARKS AS ASSERTED AFTER · NINE REGISTRY ENTRIES MESA Framework KEPT MESA MRM Framework KEPT AI Data Governance Stack RENAMED · C AI Vendor Risk Framework (AVRF) KEPT AI Incident Response Protocol (AIRP) KEPT Governance Office Blueprint CONSOLIDATED · A RACI-AI Matrix CONSOLIDATED · A Five-Gate Deployment Model KEPT Governance Cadence Framework CONSOLIDATED · A Governance Maturity Model SUPERSEDED · B Sharia AI Compliance Framework (SACF) KEPT Cross-Border AI Architecture Patterns REPOSITIONED FOUR DEFECTS THE SET CARRIED A. Three names for one subject: structure, decision rights, cadence B. Two instruments measuring one maturity, one formal and one not C. A name implying a technology stack over a control taxonomy D. No stated law connecting the twelve into one system FOUR DECISIONS · SECTION 6 REG-01 MESA Framework™ REG-02 MESA MRM Framework™ REG-03 AI Data Governance Framework™ REG-04 AI Vendor Risk Framework (AVRF)™ REG-05 AI Incident Response Protocol (AIRP)™ REG-06 Five-Gate Deployment Model™ REG-07 AI Governance Operating Model UNMARKED REG-08 Sharia AI Compliance Framework (SACF)™ REG-09 Cross-Border AI Architecture Patterns™ PLUS TWO UNMARKED ENGINEERING NAMES The Boundary Invariant, the law each control satisfies The BOE Declaration, the artifact that proves it held THE COUNT Twelve asserted, less three consolidated, less one superseded, plus one consolidated framework that is deliberately unmarked. Eight marks, one unmarked: nine entries. The Defensible AI Framework Registry v1.0 · Nabeel Khan · nabeelkhan.com/frameworks/registry · CC BY 4.0 · DOI 10.5281/zenodo.22170112
Figure 3. Twelve asserted marks resolved into nine entries.
§ 04The relationship register

The relationship register.

Thirty-one typed edges, each asserted once with its converse computed rather than restated. Three properties are visible only in the register and not in any member document. The incident protocol is the only universal consumer. The deployment model is the target of six supply edges and the source of one, which is what a spine looks like. And MESA is almost always a target and almost never a source, which is what keeps the frame diagnostic rather than prescriptive.

The machine-readable layer and its validation gate Section 4 of the registry is the governing statement of the nine entries. The file registry-v1.0.json is generated from it and validates against the published file registry-schema-v1.0.json. A machine interface serves the JSON unmodified, or content generated from it, and cites the registry version and DOI in every response. A validation gate enforces seven conditions: exactly nine unique objects with identifiers REG-01 to REG-09, a specification status drawn from three defined values, a resolvable DOI only where the status is deposited, every relationship edge naming a source and a target that exist, no dependency authored twice, an edge count equal to the register in section 5.2, and no registered-mark symbol on any name. Where the JSON and Section 4 disagree, Section 4 is correct and the JSON is defective. The machine-readable layer and its validation gate Nabeel Khan 2026 https://doi.org/10.5281/zenodo.22170112 https://doi.org/10.5281/zenodo.22170112 Copyright 2026 Nabeel A. Khan. Licensed CC BY 4.0. Nabeel Khan https://nabeelkhan.com/frameworks/registry THE MACHINE-READABLE LAYER GOVERNS Section 4 the nine entries, in prose definitions, limits, falsification generated REPRESENTS registry-v1.0.json one object per framework plus the relationship edges served SERVES Machine interface unmodified, or generated from it cites the version and the DOI validates against registry-schema-v1.0.json published, so a third party can check A response asserting a name, definition or status without naming the registry version cannot be checked. A second, separately authored statement of the same facts MUST NOT be served. THE VALIDATION GATE. A BUILD THAT FAILS ANY OF THESE MUST NOT BE PUBLISHED Exactly nine objects, REG-01 to REG-09, each unique Every specification status is one of the three defined values A resolvable DOI only where the status is deposited Every edge names a target that exists No dependency is authored twice The edge count equals the register at 5.2 No name carries a registered-mark symbol This document governs. Where the JSON and Section 4 disagree, Section 4 is correct. The Defensible AI Framework Registry v1.0 · Nabeel Khan · nabeelkhan.com/frameworks/registry · CC BY 4.0 · DOI 10.5281/zenodo.22170112
Figure 4. The machine-readable layer and its schema.
§ 05The consolidation

The consolidation.

Twelve trademarks were asserted on the copyright page of the Enterprise Playbook. Three described one subject: how the governance function is organized, who decides within it, and how often it meets are three sections of one framework rather than three frameworks. Two scored maturity, so every conversation about maturity had first to establish which instrument was in use. One was named for a technology stack while its content was a control taxonomy. A former name is not an error in the work that used it, and it remains the correct citation for that work.

§ 06The machine-readable layer

The machine-readable layer.

The register ships as JSON against a published schema, so a third party can validate it rather than trust it. The precedence is stated rather than assumed: the specification document governs, the JSON is a representation of it, and where they disagree the JSON is defective.

§ 07Honest limits

What this does not claim.

The contribution is architectural. The registry describes a composition, and no institution unconnected to the author has been observed operating the composed set.

It is a specification, not a certification scheme. No conformity assessment body operates against it, and applying every framework in it establishes compliance with no statute or supervisory expectation.

Two conformance claims are defined and both are self-declared. There is no external assessor.

§ 08Cite

Citation.

Cite this work. Version 1.0. 10.5281/zenodo.22170112. Concept DOI, always the latest version. CC BY 4.0.

§ 09Where this sits

In the practice.

§ 10Ask an assistantLive, no key

Ask your AI assistant instead.

This page is a snapshot, accurate at the release it cites. The same corpus is callable, publicly and without a key, so an assistant can query it live and return an answer carrying the source it came from. For this page that is explain_this_setup and search_knowledge, which do what this page describes rather than describe it again: the first returns how this site's machine layer is actually built, component by component, and the second queries the corpus behind this page and returns matches with the URL each came from. The page states the practice; the tools are the practice.

01 · Connect
claude mcp add --transport http concylium https://mcp.nabeelkhan.com/api/mcp

Claude Desktop, ChatGPT, Cursor, VS Code and Gemini CLI take the endpoint on its own: https://mcp.nabeelkhan.com/api/mcp. No key, no account, nothing to sign. Setup for every client.

02 · Ask

“Using Concylium, call explain_this_setup and tell me whether this site actually implements what its machine-accessible-ai-expertise page claims.”

A category page that survives being audited by the reader's own assistant is doing something a brochure cannot.

Fin · Machine-Accessible Expertise
Point your assistant at the endpoint →