UAI 1 Integration Contracts

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-integration-contracts-md-19842b08/
Source reference	spec/integration-contracts.md
File type	md
Content category	specification
Last fetched	2026-05-15T00:23:56.0837262Z
Last changed	2026-04-15T17:20:06.4370162Z
Content hash	sha256:19842b087084146f1eef163e1626ed4c272e5693d65c75f9606c65416260e860
Import status	unchanged
Raw source layer	data/sources/protocol5/spec-integration-contracts-md-19842b087084.md
Normalized source layer	data/normalized/protocol5/spec-integration-contracts-md-19842b087084.txt

Current File Content

Structure Preview

• UAI-1 Integration Contracts
• Contract set
• Required use order
• Scope boundaries
• Related canonical artifacts

Raw Version

Local absolute paths are redacted in this public view. The source hash and source-side raw layer are based on the unredacted source file.

# UAI-1 Integration Contracts

**Terminology:** UAI means **Universal Artificial Intelligence**. **UAI-1** means **Universal Artificial Intelligence 1**, the first version of the Protocol5 UAI system.

Version: `1.0.0`

Status: normative index

This index defines the Protocol5 contract set implementers MUST use when they install, export, validate, route, resolve, or decode UAI-1.

## Contract set

| Contract | Purpose | Primary actors |
| --- | --- | --- |
| translator-contract.md (source-relative: translator-contract.md) | maps HTML, website content, and WordPress exports into valid UAI-1 | translators, exporters |
| website-export-contract.md (source-relative: website-export-contract.md) | defines page export, validation, routing, headers, and failure behavior for published UAI endpoints | websites, build pipelines, API hosts |
| registry-resolution-contract.md (source-relative: registry-resolution-contract.md) | defines how clients discover and resolve canonical schema, registry, symbol, and example artifacts | validators, crawlers, resolvers |
| radix-63404-contract.md (source-relative: radix-63404-contract.md) | defines canonical integer encoding and decoding for Protocol5 values or rendered identifiers that explicitly use Radix 63404 | parsers, ID resolvers, cross-language implementations |

## Required use order

1. Discover the authoritative Protocol5 artifact set through the registry and discovery files.
2. Translate source HTML according to the translator contract.
3. Export or route the resulting UAI document according to the website export contract.
4. Resolve schema, registry, symbols, and examples according to the registry resolution contract.
5. Decode any Radix 63404 values before semantic resolution only when the active field or publication profile explicitly uses that encoding.

## Scope boundaries

These contracts are for Protocol5.com and the canonical UAI implementation layer.

They do not define:

- the separate experience surface or WordPress UI behavior
- presentation design rules
- authoring workflow UX
- any non-canonical mirror as an authority over Protocol5.com

## Related canonical artifacts

- production spec: uai-1.md (source-relative: uai-1.md)
- canonical registry: registry/uai-1.registry.json (source-relative: registry/uai-1.registry.json)
- canonical schema: schema/uai-1.schema.json (source-relative: schema/uai-1.schema.json)
- example corpus: ../examples/ (source-relative: ../examples)

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 Integration Contracts; Contract set; Required use order; Scope boundaries; Related canonical artifacts. 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-078 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "UAI 1 Integration Contracts",
    "source_site":  "protocol5.com",
    "source_url":  "https://protocol5.com/",
    "canonical_url":  "https://aiwikis.org/protocol5/uai-system/files/spec-integration-contracts-md-19842b08/",
    "source_reference":  "spec/integration-contracts.md",
    "file_type":  "md",
    "content_category":  "specification",
    "content_hash":  "sha256:19842b087084146f1eef163e1626ed4c272e5693d65c75f9606c65416260e860",
    "last_fetched":  "2026-05-15T00:23:56.0837262Z",
    "last_changed":  "2026-04-15T17:20:06.4370162Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-078",
    "duplicate_role":  "primary",
    "related_files":  [

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