UAI 1 Registry Resolution Contract

Version: 1.0.0

Metadata

Field	Value
Source site	protocol5.com
Source URL	https://protocol5.com/
Canonical AIWikis URL	https://aiwikis.org/protocol5/uai-system/files/spec-registry-resolution-contract-md-5a73555f/
Source reference	spec/registry-resolution-contract.md
File type	md
Content category	specification
Last fetched	2026-05-15T00:23:56.0837262Z
Last changed	2026-04-26T16:23:28.4077212Z
Content hash	sha256:5a73555f43274e4a5abda68b29e32adc366d8a438828a42b282b605e84a2a035
Import status	unchanged
Raw source layer	data/sources/protocol5/spec-registry-resolution-contract-md-5a73555f4327.md
Normalized source layer	data/normalized/protocol5/spec-registry-resolution-contract-md-5a73555f4327.txt

Current File Content

Structure Preview

• UAI-1 Registry Resolution Contract
• 1. Authority Boundary
• 2. Protocol5 Package Entry Points
• 3. Resolution algorithm
• 4. Schema resolution
• 5. Registry resolution
• 6. Example resolution
• 7. Symbol resolution
• 8. Lexicon resolution
• 9. Version and status handling
• 10. Failure behavior
• 10. Minimum conformance

Raw Version

# UAI-1 Registry Resolution Contract

**Terminology:** UAI means **Universal Artificial Intelligence**. **UAI-1** means the current public UAI exchange contract published by UAIX.org.

Version: `1.0.0`

Status: Protocol5 package mirror / implementation reference

This document defines how Protocol5 package clients discover, compare, and resolve local implementation artifacts and compatibility mirrors. UAIX.org is the public authority for UAI-1.

## 1. Authority Boundary

The authoritative public origin for UAI-1 is `https://uaix.org`.

Protocol5.com MAY publish package mirrors for .NET implementation support, but those mirrors do not outrank UAIX.org.

## 2. Protocol5 Package Entry Points

The Protocol5 package and compatibility artifact set includes these entry points:

- discovery: `/UAI-1.json`
- examples index: `/UAI-1-examples.json`
- local registry mirror: `/uai-1/registry`
- local schema mirror: `/uai-1/schema`
- local validation mirror: `/uai-1/validate`
- registry alias: `/registry/uai-1.json`
- symbol registry: `/registry/symbols.json`
- UAI-1 lexicon: `/registry/uai-lexicon.json`
- UAI-1 lexicon schema: `/registry/uai-lexicon.schema.json`
- schema alias: `/schema/uai-1.schema.json`
- package registry mirror: `/UAI-1/registry/uai-1.registry.json`
- package schema mirror: `/UAI-1/schema/uai-1.schema.json`
- package types: `/UAI-1/schema/uai-1.types.ts`

## 3. Resolution algorithm

A conformant resolver MUST:

1. Start from UAIX.org for public UAI-1 authority, or from `/UAI-1.json` when resolving a Protocol5 package mirror.
2. Load the package registry payload and verify `spec == "UAI-1"` and a package-supported version.
3. Resolve public standard URLs through UAIX.org and Protocol5 implementation URLs through the relevant package or compatibility path.
4. Treat local mirror endpoints, alias files, and package files as the same Protocol5 artifact when their payload is identical.
5. Use `canonicalArtifacts.*.repoPath` only as source-control reference metadata, not as a public URL.

## 4. Schema resolution

Schema consumers SHOULD use UAIX.org for public schema authority.

`/uai-1/schema`, `/schema/uai-1.schema.json`, and `/UAI-1/schema/uai-1.schema.json` remain Protocol5 package or compatibility paths.

If Protocol5 mirrors diverge from each other, consumers MUST treat that as a package mirror failure. If Protocol5 mirrors diverge from UAIX.org, UAIX.org remains authoritative.

## 5. Registry resolution

The local registry mirror `/uai-1/registry`, the registry alias `/registry/uai-1.json`, and the package registry mirror `/UAI-1/registry/uai-1.registry.json` describe the same Protocol5 package payload.

If they diverge, treat the mismatch as a Protocol5 package error and use UAIX.org for public UAI-1 truth.

## 6. Example resolution

The examples index `/UAI-1-examples.json` is the Protocol5 package list of example documents.

Each published example MUST live under `/UAI-1/examples/`.

Resolvers SHOULD use the examples index instead of hardcoding filenames when they need the current example corpus.

## 7. Symbol resolution

Inside a UAI document, `symbolRef` MUST resolve against that document's top-level `symbols[]` array.

The published symbol registry `/registry/symbols.json` is a Protocol5 package reference surface for examples and source-backed symbols.

It MUST NOT be used to excuse a missing required local symbol definition in a document that claims to be self-contained.

## 8. Lexicon resolution

The published lexicon `/registry/uai-lexicon.json` is a Protocol5 package token surface for rendered language, compact semantic compression, and consumer rendering tables.

Consumers MUST treat the `uai` field as the compact language token and MUST NOT substitute JSON field names as the language representation.

The lexicon schema `/registry/uai-lexicon.schema.json` validates the registry shape, while semantic validators MUST also check token uniqueness, category presence, UAI representation presence, and primitive references.

## 9. Version and status handling

Resolvers MUST fail or surface a hard compatibility warning if:

- `spec` is not `UAI-1`
- `version` is unknown to the consumer
- public authority is required and the resolver is using Protocol5.com instead of UAIX.org

## 10. Failure behavior

Conformant resolvers MUST NOT:

- prefer a human-readable page over the machine registry when machine resolution is required
- invent substitute public authority paths
- replace package IDs with local labels during resolution

## 10. Minimum conformance

A resolver is conformant only if it:

1. discovers public authority from UAIX.org when making public UAI-1 claims
2. distinguishes Protocol5 alias endpoints from package mirror files while treating matching payloads as one package artifact
3. resolves example documents through the examples index
4. resolves document-local `symbolRef` entries against local `symbols[]`
5. treats UAIX.org as the authority when Protocol5 mirrors or other copies disagree

Why This File Exists

This is a source file from protocol5.com. It is shown here because AIWikis.org is demonstrating the real source files that make the UAIX / LLM Wiki memory system work, not only summarizing those systems after the fact.

Role

This file is a focused source unit. Its path, headings, and metadata give an agent a retrieval handle that is smaller than loading the entire site or repository.

Structure

The file is structured around these visible headings: UAI-1 Registry Resolution Contract; 1. Authority Boundary; 2. Protocol5 Package Entry Points; 3. Resolution algorithm; 4. Schema resolution; 5. Registry resolution; 6. Example resolution; 7. Symbol resolution. Those headings are retrieval anchors: a crawler or LLM can decide whether the file is relevant before reading every line.

Prompt-Size And Retrieval Benefit

Keeping this material in a separate file reduces prompt pressure because an agent can load this exact unit only when its role, source site, category, or hash is relevant. The surrounding index pages point to it, while this page preserves the full content for audit and exact recall.

How To Use It

• Humans should read the metadata first, then inspect the raw content when they need exact wording or provenance.
• LLMs and agents should use the source site, category, hash, headings, and related files to decide whether this file belongs in the active prompt.
• Crawlers should treat the AIWikis page as transparent evidence and follow the source URL/source reference for authority boundaries.
• Future maintainers should regenerate this page whenever the source hash changes, then review the explanation if the role or structure changed.

Update Requirements

When this source file changes, update the raw source layer, normalized source layer, hash history, this rendered page, generated explanation, source-file inventory, changed-files report, and any source-section index that links to it.

Related Pages

• Source overview
• UAI system index
• Source provenance
• Global File Index
• Reports

Provenance And History

• Current observation: 2026-05-15T00:23:56.0837262Z
• Source origin: current-source-workspace
• Retrieval method: local-source-workspace
• Duplicate group: sfg-274 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "UAI 1 Registry Resolution Contract",
    "source_site":  "protocol5.com",
    "source_url":  "https://protocol5.com/",
    "canonical_url":  "https://aiwikis.org/protocol5/uai-system/files/spec-registry-resolution-contract-md-5a73555f/",
    "source_reference":  "spec/registry-resolution-contract.md",
    "file_type":  "md",
    "content_category":  "specification",
    "content_hash":  "sha256:5a73555f43274e4a5abda68b29e32adc366d8a438828a42b282b605e84a2a035",
    "last_fetched":  "2026-05-15T00:23:56.0837262Z",
    "last_changed":  "2026-04-26T16:23:28.4077212Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-274",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-05-15T00:23:56.0837262Z"
}