Authority Resolution Model¶

Universal verification architecture for regulated competence across any domain

Field	Value
Status	FOUNDATIONAL — Core intellectual property
Version	1.0
Date	March 2026
Classification	CONFIDENTIAL
Authors	Tim Rignold, Claude (Anthropic)

This document describes the foundational architecture of UCCA's verification system. It is the intellectual property core of the company. The model described here is domain-agnostic and applies to any regulated environment where entities must prove competence to operate.

Section 1 — The Problem¶

In every regulated industry — education, aviation, defence, medical, nuclear, financial services — the same fundamental problem exists: an entity (human, organisation, or machine) must prove it is competent to operate within a defined scope, and that proof must be verifiable, auditable, and traceable to a legitimate authority.

Today, this problem is solved independently in each domain. Each industry builds its own compliance systems, its own audit frameworks, its own evidence management. The result is thousands of siloed verification systems that all solve the same structural problem in different ways, with no interoperability and no shared architecture.

UCCA's thesis is that the underlying structure of regulated competence is universal. The names change. The content changes. The shape does not.

Section 2 — Three-Dimensional Regulatory Architecture¶

Analysis of legislative frameworks across regulated industries reveals a consistent three-dimensional structure. This is not coincidental — it is a necessary consequence of governing competence in complex systems.

The Three Axes¶

Every regulatory system exists as a three-dimensional object with these axes:

Axis 1: Authority (X) — What power exists and who holds it¶

The primary legislation that creates the regulatory authority, defines its powers, establishes what entities must comply with, and sets the consequences for non-compliance. This is the load-bearing structure. It defines the WHY.

Australian VET: National Vocational Education and Training Regulator Act 2011
Aviation: Civil Aviation Act 1988
Medical: Health Practitioner Regulation National Law
Autonomous systems (emerging): Product safety legislation, AI governance frameworks

Axis 2: Transition (Y) — How power moves through time¶

The transitional provisions that manage change. How existing registrations migrate when regulations change. How pending applications transfer between authorities. How timelines and grace periods work. This axis allows the system to rotate without breaking — you can change the regulatory structure while entities continue to operate.

Australian VET: NVR (Transitional Provisions) Act 2011
Aviation: Transition schedules when CASA regulations change
Medical: Transitional provisions when professions move to national regulation

Axis 3: Integration (Z) — How power connects to adjacent systems¶

The consequential amendments that reach into every adjacent piece of legislation and rewire references. When you change one part of a regulatory system, you must update every system that touches it. This axis maintains coherence across the entire legislative landscape.

Australian VET: NVR (Consequential Amendments) Act 2011 — rewires ESOS Act, Higher Education Support Act, Indigenous Education Act
Aviation: Consequential amendments to air navigation, airport, and safety investigation legislation
Medical: Amendments to Medicare, pharmaceutical benefits, and health insurance legislation

Why Three Dimensions Are Necessary¶

A regulatory system cannot be flat. A single document cannot simultaneously define authority, manage change over time, and maintain integration with adjacent systems. The three dimensions provide three independent degrees of freedom:

Adjust what is authorised (authority axis) without breaking transition timelines
Manage temporal change (transition axis) without rewriting the authority structure
Rewire adjacent system connections (integration axis) without altering the core authority or transition logic

This is not a design choice — it is a structural requirement. Any attempt to flatten it creates either rigidity (can't change), inconsistency (changes break adjacent systems), or gaps (transitions are unmanaged).

Section 3 — The Regulatory Cascade¶

Within the authority axis, regulated industries exhibit a consistent cascade pattern. The legislation defines the mandate. The regulator interprets the mandate into operational frameworks. The frameworks decompose into atomic competency specifications. Each layer serves a distinct purpose and does not overlap with the others.

Layer 1: Legislative Authority¶

The Act of Parliament (or equivalent sovereign instrument) that creates the regulatory power. It establishes:

The regulator and its powers
What entities must comply
The quality framework (by reference, not by detail)
The enforcement cascade (audit → direction → sanction → suspension → cancellation)
The public register
Offences and penalties

This layer says: you MUST. It does not say how.

Layer 2: Regulatory Framework¶

The regulator takes the legislative mandate and cascades it into operational standards. These are the instruments the regulator creates under powers granted by the Act:

Outcome standards
Compliance standards
Credential policy
Financial viability
Data provision
Qualifications framework

This layer says: here is HOW you demonstrate compliance.

Layer 3: Competency Specification¶

The atomic units of competence. Each specification defines exactly what an entity must demonstrate:

Performance criteria — what the entity must DO
Knowledge evidence — what the entity must KNOW
Performance evidence — what the entity must PROVE

This layer says: here is WHAT competence looks like at the atomic level.

Section 4 — Universal Primitives¶

Extracting the domain-specific language from the Australian VET system reveals seven universal primitives that appear in every regulated competence domain:

Primitive 1: Authority Grant¶

A recognised authority grants an entity the right to operate within a defined scope.

VET: ASQA registers an RTO.
Aviation: CASA issues an Air Operator's Certificate.
Medical: AHPRA registers a practitioner.
Machine: A certification body certifies an autonomous system for a defined operating envelope.

Primitive 2: Scope Boundary¶

The authority grant defines exactly what the entity is permitted to do. The scope is finite, explicit, and auditable.

Primitive 3: Compliance Framework¶

The regulatory authority defines a set of standards that the entity must continuously comply with.

Primitive 4: Competency Specification¶

The atomic unit of competence. A specification that defines what the entity must know, what it must do, and what evidence it must produce.

Primitive 5: Evidence Anchor¶

Every claim of competence must be anchored to verifiable evidence. Without evidence, competence is an assertion, not a fact.

Primitive 6: Verification Event¶

The authority periodically verifies that the entity continues to comply. This is the audit.

Primitive 7: Enforcement Cascade¶

When compliance fails, a graduated enforcement mechanism activates. The cascade is always graduated: identify → notify → direct to rectify → restrict scope → suspend → cancel.

The Seven Primitives — Summary¶

#	Primitive	Question It Answers	Engine Object
1	Authority Grant	Who says this entity can operate?	`authority_grant`
2	Scope Boundary	What is this entity permitted to do?	`scope_boundary`
3	Compliance Framework	What standards must be met?	`compliance_framework`
4	Competency Specification	What does competence look like?	`capability_object`
5	Evidence Anchor	How is competence proven?	`evidence_anchor`
6	Verification Event	How is compliance checked?	`verification_event`
7	Enforcement Cascade	What happens when compliance fails?	`enforcement_action`

Section 5 — Man, LLM, Machine¶

The seven primitives apply identically regardless of whether the entity being verified is a human professional, an AI system, or an autonomous machine.

Human (Man)¶

A nurse in an aged care facility. Authority grant from AHPRA registration. Scope boundary is their scope of practice. Compliance framework is the Nursing and Midwifery Board's professional practice standards. Competency specification is the set of competencies for their registration category. Evidence anchor is their CPD portfolio. Verification event is periodic registration renewal. Enforcement cascade runs from conditions on practice through to cancellation.

AI System (LLM)¶

A large language model deployed in a medical advice context. Authority grant from whatever regulatory framework governs AI in healthcare (emerging). Scope boundary defines what the system is certified to do: answer general health questions but not diagnose. etc.

Autonomous Machine¶

A domestic care robot assisting an elderly person. Authority grant from product safety certification. Scope boundary defines: assist with mobility, monitor vitals, alert emergency services — but not administer medication. etc.

The Universal Pattern¶

In each case, the entity:

Receives authority to operate from a recognised source
Operates within a defined and bounded scope
Must continuously comply with an externally defined framework
Demonstrates competence against atomic specifications
Provides verifiable evidence for every capability claim
Submits to periodic verification
Faces graduated consequences for non-compliance

The engine that processes these seven primitives does not need to know whether the entity is a person, an algorithm, or a robot.

Section 6 — UCCA Engine Architecture¶

The UCCA engine is the domain-agnostic processing system that operates on the seven universal primitives.

Engine Responsibilities¶

Ingest, Validate, Fingerprint, Emit.

What the Engine Does NOT Do¶

It does not know about Australian VET, aviation, defence, or any specific domain.
It does not query training.gov.au, CASA, AHPRA.
It does not interpret domain-specific regulations.
It does not make subjective judgements.
It does not generate content.

The engine is deterministic.

World Layer Responsibilities¶

Data acquisition
Authority resolution
Evidence collection
Surface delivery

The Separation Principle¶

The world knows the domain. The engine knows the structure. They never cross.

Section 7 — World Onboarding¶

Bringing a new regulated domain into UCCA requires resolving that domain's regulatory architecture into the universal model.

Step 1: Identify the Three Axes
Step 2: Map the Regulatory Cascade
Step 3: Extract the Seven Primitives
Step 4: Build the Translation Layer
Step 5: Load Authority Data
Step 6: Verify End-to-End

Section 8 — Why This Matters¶

For Human Competence¶

The verification architecture applies to every regulated profession — nursing, aviation, construction, financial advice — anywhere a human must prove competence to operate.

For AI Systems¶

As AI governance frameworks emerge, the same seven primitives will define what an AI system is authorised to do, what evidence it must produce, and how compliance is verified.

For Autonomous Machines¶

Robotics, autonomous vehicles, and industrial automation all require the same structural proof of competence within defined boundaries.

The Market¶

The first world is Australian VET (RTOpacks). Every pattern validated in AU VET applies directly to the next world.

UCCA is not an education tool. It is not a compliance engine. It is the universal verification architecture for regulated competence — regardless of whether the entity being verified is a human, an algorithm, or a machine.

Version History¶

Version	Date	Change	Author
1.0	2026-03-03	Initial document	Tim Rignold / Claude
1.1	2026-03-11	Filed to knowledge site with frontmatter	Claude Code