AI GOVERNANCE REGISTRY

Preserve what a governance system is, what it claims, and what it cannot claim.

Governance cannot remain inspectable when its identity, stewardship, versions, claims, evidence, review history, and supersession status are scattered across websites, presentations, policies, and private documents. The registry creates a public proof surface for governance identity and continuity.

Registration does not equal validation.

A registry entry preserves declared facts, evidence references, review status, and limitations. Inclusion does not certify effectiveness, legality, safety, truth, or regulatory compliance.

Registry entries4

Current demonstration records across frameworks, systems, and review methods.

Active entries2

Entries currently declared active by their steward.

Under review2

Entries with unresolved independent review requirements.

Core boundaryNO SELF-CERTIFICATION

Steward declarations remain separate from independent review and public acceptance.

WHY A REGISTRY EXISTS

Governance identity must remain continuous before governance claims can be tested.

A system cannot be meaningfully reviewed when reviewers do not know which version is being assessed, who controls it, what evidence supports its claims, what changed, or whether the current implementation has superseded earlier public descriptions.

Identity

The exact governance system, framework, model, method, or standard being represented.

Stewardship

The person or institution accountable for maintaining the entry and declaring changes.

Claims

What the registered system affirmatively says it can do.

Non-claims

What the system does not prove, decide, certify, replace, or authorise.

Evidence

The records, artifacts, tests, publications, demonstrations, and review materials supporting the entry.

Continuity

Versions, effective dates, supersession, withdrawal, and current operational status.

PUBLIC REGISTRY SURFACE

Inspect entries by identity, status, type, claim, or evidence.

4 registry entry or entries
Governance FrameworkTA-14-REG-0001
ACTIVE

TA-14 Admissible Execution Architecture

Structures consequential execution through evidence, continuity, admissibility, authority, binding, commitment, execution, and outcome records.

Declared claims
  • Defines a bounded route for consequential execution
  • Separates evidence from determination and execution
  • Supports ALLOW, HOLD, DENY, and ESCALATE outcomes
Declared non-claims
  • Does not independently establish legal compliance
  • Does not certify factual truth without admissible evidence
  • Does not replace domain-specific professional judgment
Evidence references
  • Published architecture records
  • Demonstration routes
  • Verification receipts
  • Replay and continuity tests
Review and version continuity
  • Independent review pending expansion
  • v1.0
  • v1.1
  • v2.0 architecture route
Review MethodTA-14-REG-0002
UNDER REVIEW

Article 50 Transparency Assessment Route

Maps provider and deployer transparency pathways for direct interaction, marking, detectability, deepfakes, and public-interest text.

Declared claims
  • Separates provider and deployer duties
  • Maps declared evidence and unresolved gaps
  • Preserves implementation and review boundaries
Declared non-claims
  • Does not provide legal advice
  • Does not certify Article 50 compliance
  • Does not submit evidence to authorities
Evidence references
  • Article 50 pathway records
  • Disclosure evidence maps
  • Detectability test requirements
  • Exception and limitation records
Review and version continuity
  • Legal review required
  • Technical review required
  • Initial public workspace
Review MethodTA-14-REG-0003
ACTIVE

High-Risk AI Lifecycle Governance Route

Structures classification, risk management, data governance, documentation, logging, oversight, conformity, deployment, monitoring, and incident response.

Declared claims
  • Represents high-risk governance as a lifecycle
  • Defines evidence gates and failure states
  • Connects classification to operation and outcome
Declared non-claims
  • Does not classify a real system by itself
  • Does not complete conformity assessment
  • Does not issue registration or CE marking
Evidence references
  • Lifecycle gate definitions
  • Failure-state records
  • Governed-output definitions
  • Deployment and monitoring pathways
Review and version continuity
  • Sector review required
  • Conformity review required
  • Initial high-risk workspace
AI SystemTA-14-REG-0004
UNDER REVIEW

Governed Record Interpreter

Produces bounded interpretations of governed records while preserving what the source record proves, does not prove, and requires for further review.

Declared claims
  • Separates source record from interpretation
  • Preserves evidentiary boundaries
  • Supports governed interpretation outputs
Declared non-claims
  • Does not diagnose
  • Does not optimise
  • Does not replace licensed or clinical judgment
Evidence references
  • Record-type definitions
  • Interpretation workflow
  • Admissibility and continuity fields
  • Governed Interpretation Record specification
Review and version continuity
  • Environmental review pending
  • Clinical review required for medical use
  • GRI initial architecture
REQUIRED REGISTRY RECORDS

A credible entry requires more than a title and a description.

Identity Record

Name, registry ID, type, scope, steward, establishment date, and current status.

Claim Record

Every material capability, purpose, assertion, and declared governance outcome.

Non-Claim Record

Explicit boundaries showing what the registered system cannot establish or replace.

Evidence Record

Artifacts, publications, demonstrations, tests, records, and proof references supporting each claim.

Review Record

Reviewer identity, scope, evidence inspected, objections, corrections, findings, and limitations.

Version Record

Current version, prior versions, effective dates, material changes, supersession, and withdrawal.

Stewardship Record

Who maintains the entry, who may change it, and who must answer for inaccurate declarations.

Public Challenge Record

Disputes, corrections, counter-evidence, unresolved objections, and final disposition.

REGISTRY LIFECYCLE

Every entry should move through visible states.

01

Declared

The steward submits identity, claims, non-claims, evidence, and version information.

02

Evidence mapped

Each material claim is bound to inspectable evidence or marked unsupported.

03

Under review

Independent reviewers inspect scope, evidence, reasoning, and boundaries.

04

Active

The entry is current, attributable, and open to inspection and challenge.

05

Superseded

A later version replaces the entry while preserving prior public history.

06

Withdrawn

The steward or authority removes active standing without erasing the record.

CONNECTED EXCHANGE SURFACES

The registry identifies the system. Other workspaces test and preserve the route.

PUBLIC CLAIMS REQUIRE PUBLIC CONTINUITY

A governance system should not be able to change invisibly after people rely on it.

The registry makes stewardship, claims, evidence, review, versions, corrections, supersession, and withdrawal visible so governance identity can remain inspectable over time.

TA-14 Exchange Activity

Public activity recorded across the Exchange

Visitors

Page Views