Skip to content
AIWikis.org

UAIX Workspace

Publication Warning This page is marked noindex and should not be treated as canonical public authority.

Adds the UAIX L0-L6 agent capability framework, memory firewall, quarantine-first import guidance, authority boundaries, seven evaluation packet templates, schemas, fixtures, discovery files, docs, validation script,...

Metadata

FieldValue
Source siteuaix.org
Source URLhttps://uaix.org/
Canonical AIWikis URLhttps://aiwikis.org/uaix/files/readme-md-939d1d36/
Source referenceREADME.md
File typemd
Content categorymemory-file
Last fetched2026-06-22T01:56:21.9510185Z
Last changed2026-06-21T20:28:13.4833227Z
Content hashsha256:939d1d362728b493a36e235a4f5c48700201fe10d4a23dce9e363a2348f00119
Import statuschanged
Raw source layerdata/sources/uaix/readme-md-939d1d362728.md
Normalized source layerdata/normalized/uaix/readme-md-939d1d362728.txt

Current File Content

Structure Preview

  • 3.117.0 - Agent Capability Alignment
  • 3.114.0 - Agent Capability Alignment
  • 3.65.0 - Agent Capability Alignment
  • 2026-06-10 - Memory Maintenance And Protected Artifact Boundary
  • 3.67.0 - Launch-Baseline Required File Set
  • 3.66.0 - API Reference And Discovery Hotfix
  • 3.65.0 - Workspace Version Authority Alignment
  • 3.63.0 - Required Anchor Draft
  • 3.62.0 - Agent Capability Alignment
  • UAIX Workspace
  • Status
  • Purpose
  • AI Quick Start
  • Public UAI Reading Path
  • Progressive Navigation
  • Current Project Truth
  • Canonical Docs
  • Background And Helper Docs
  • Do Not Load By Default
  • Repo Map
  • Markdown Conventions
  • Scope Note
  • UAIX Standards Release 3.80.0
  • UAIX Chatbot Access and GET-Action Pattern

Raw Version

This public page shows a bounded preview of a large source file. The complete source remains in the raw and normalized source layers named in metadata, with the SHA-256 hash above for verification.

  • Source characters: 26394
  • Preview characters: 11907

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


## 3.117.0 - Agent Capability Alignment

Adds the UAIX L0-L6 agent capability framework, memory firewall, quarantine-first import guidance, authority boundaries, seven evaluation packet templates, schemas, fixtures, discovery files, docs, validation script, and release evidence for v3.117.0. UAIX remains a standards and evidence surface, not a runtime execution or certification authority.


## 3.114.0 - Agent Capability Alignment

Adds the UAIX L0-L6 agent capability framework, memory firewall, quarantine-first import guidance, authority boundaries, seven evaluation packet templates, schemas, fixtures, discovery files, docs, validation script, and release evidence for v3.114.0. UAIX remains a standards and evidence surface, not a runtime execution or certification authority.


## 3.65.0 - Agent Capability Alignment

Adds the UAIX L0-L6 agent capability framework, memory firewall, quarantine-first import guidance, authority boundaries, seven evaluation packet templates, schemas, fixtures, discovery files, docs, validation script, and release evidence for v3.65.0. UAIX remains a standards and evidence surface, not a runtime execution or certification authority.

## 2026-06-10 - Memory Maintenance And Protected Artifact Boundary

Makes `.uai/memory-maintenance.uai`, `.uai/identity.uai`, `.uai/world-context.uai`, `.uai/totem.uai`, `.uai/taboo.uai`, `.uai/talisman.uai`, and `.uai/short-term-memory.uai` the universal required launch-baseline files for every UAIX memory or handoff package. `.uai/totem.uai`, `.uai/taboo.uai`, and `.uai/talisman.uai` are active instruction anchors that must be read and obeyed before broad execution. The default `.uai/totem.uai` also carries the recursive Suggested Next Prompt contract: accepted work must end with a visible, copy-paste-ready prompt containing `Feature/improvement focus`, `Code/source changes`, and `Automated tests/checks` sections plus concrete next work or an explicit no-op/source-validation stop condition. Suggestions and permission requests are allowed; changing, deleting, weakening, replacing, or bypassing an anchor is forbidden unless a human directly names the exact artifact and exact operation.

Public detail pages: `/en-us/ai-memory/uai-files/memory-maintenance-uai/` for the universal memory lifecycle and protected-path policy, and `/en-us/ai-memory/uai-files/next-recursive-prompt-uai/` for the code-scope derived continuation artifact.

## 3.67.0 - Launch-Baseline Required File Set

Superseded by the 2026-06-10 memory-maintenance rule above. Current universal required files are `.uai/memory-maintenance.uai`, `.uai/identity.uai`, `.uai/world-context.uai`, and `.uai/short-term-memory.uai`. Project/developer packages and packages that declare code, automation, executable workflow, or code-like artifacts require `.uai/coding-standards.uai` and `.uai/next-recursive-prompt.uai`. Adds closed file-set semantics to wizard output, docs, local `.uai` memory, manifests, and validator guidance: every package file is universal required, profile-required, content-triggered required, configuration-specific required, or out-of-scope.

Adds the source-ready Principles Charter and Principles Role Guidance layer: `/en-us/governance/principles/`, `/en-us/governance/principles-role-guidance/`, `docs/governance/principles-traceability-matrix.md`, `docs/templates/principles-impact-assessment.md`, principle-aware AI Memory Wizard output, visitor AI digest pointers, route inventory, implementation map, public evidence manifest entries, and local `.uai` intake evidence. Rebuild packages before describing these source-only principles changes as deployed artifacts.

## 3.66.0 - API Reference And Discovery Hotfix

Rebuilds UAIX WordPress artifacts at workspace-authority version 3.66.0. The hotfix keeps full evidence bundles on dedicated routes, uses compact summary/link records for discovery and OpenAPI, and avoids eager OpenAPI construction during API Reference shortcode rendering.

Source-only updates after this package build include the Mission Statement/homepage copy, `.uai`/docs cleanup, and Principles governance layer; rebuild before describing those changes as deployed artifacts.

## 3.65.0 - Workspace Version Authority Alignment

Aligns UAIX package-visible versions, public discovery files, UAI core indexes, release guards, and regenerated WordPress review artifacts to the `[local path redacted]` coordinated package version. Public UAI-1 remains version 1.0; this is a deployment/package version alignment pass.

## 3.63.0 - Required Anchor Draft

Made protected-anchor files required in an earlier pre-launch draft. The current launch baseline is the 2026-06-11 active-anchor correction: `.uai/totem.uai`, `.uai/taboo.uai`, and `.uai/talisman.uai` are required active instruction anchors to read and obey, while changing them remains human-authorized by exact artifact and operation.

## 3.62.0 - Agent Capability Alignment

Adds the UAIX L0-L6 agent capability framework, memory firewall, quarantine-first import guidance, authority boundaries, seven evaluation packet templates, schemas, fixtures, discovery files, docs, validation script, and release evidence for v3.62.0. UAIX remains a standards and evidence surface, not a runtime execution or certification authority.

# UAIX Workspace

Updated: 2026-05-02

## Status

This is the canonical human-and-AI repo overview.

## Purpose

This repository contains the local WordPress Studio workspace for UAIX.org.

Use this file as the human-and-AI onboarding entry point for the repo.

UAI public-site and handoff work has moved out of `[local path redacted]`. Use `[local path redacted]` as the canonical local workspace for UAI-1 public materials.

## AI Quick Start

Read these files in this order:

1. `AGENTS.md`
2. `.uai/readme.human`
3. every file listed in the `Loaded Context` section of `AGENTS.md`
4. `.agents/skills/uaix-handoff/` when using Codex and the task touches the handoff bundle or file intake
5. `STUDIO.md` when the work touches WordPress Studio, WP-CLI, packaging, or runtime verification
6. `docs/current-reference.md`
7. `docs/deploy.md`
8. `docs/Mission and Site Plan for UAIX.md`
9. `docs/roadmap.md`
10. `docs/uaix-terminology.md`

Large historical research and proposal files were moved to AIWikis long-term memory on 2026-05-01. Use local stubs and compiled AIWikis nodes for routing, and open raw archived source only when original wording or older provenance is actually needed.

After loading `AGENTS.md`, `.uai/readme.human`, and the `.uai` bundle, a new AI should summarize the project in 3-5 bullets and confirm the hard constraints before making a broad change.

Before broad edits, the new AI should also name the files, routes, or docs it expects to touch and the checks it expects to run. If required `.uai` context is missing or contradictory, it should report that blocker before editing.

## Public UAI Reading Path

When the task is about explaining UAI to another AI, team, or implementer, use the public pages in this order:

1. `/en-us/ai-memory/` for the broad AI Memory standard, supported starter configuration chooser, LLM Wiki boundary, and dynamic canonical-template downloads.
2. `/en-us/ai-memory/uai-files/` for the public `.uai` File Guide, including `/en-us/ai-memory/uai-files/memory-maintenance-uai/` and `/en-us/ai-memory/uai-files/next-recursive-prompt-uai/`.
3. `/en-us/tools/ai-memory-package-wizard/` for guided package planning over supported starter bundles, package model JSON, manifest overlay JSON, copy-paste files under `.uai/`, `.uai/archives/` evidence, `.uai/exports/` artifacts including JSON-LD and llms outputs, universal required `.uai/memory-maintenance.uai`, `.uai/identity.uai`, `.uai/world-context.uai`, `.uai/totem.uai`, `.uai/taboo.uai`, `.uai/talisman.uai`, and `.uai/short-term-memory.uai`, active-anchor guidance for reading and obeying Totem, Taboo, and Talisman before broad execution, `.uai/coding-standards.uai` and `.uai/next-recursive-prompt.uai` required for Project Handoff packages, project/developer packages, and packages that declare code, automation, executable workflow, or code-like artifacts, `.uai/file-handoff.uai` required for Agent File Handoff configuration, `.uai/long-term-memory.uai` required for LLM Wiki long-memory configuration, readiness metadata, and canonical ZIP links.
4. `/en-us/specification/project-handoff/` for the practical transfer subtype built from root `AGENTS.md`, `.uai/readme.human`, and `.uai`; it is portable project memory, not an agent runtime.
5. `/en-us/guides/project-handoff-openai/` when the workflow uses OpenAI Agents, Codex, Skills, MCP, sessions, traces, approvals, or runtime handoffs and the reader needs the complementary boundary.
6. `/en-us/guides/agentic-harnesses-uai/` when the reader needs to separate agentic harness execution strategy from UAI evidence, AI Memory, Project Handoff, conformance, and support-claim boundaries.
7. `/en-us/guides/project-handoff-coding-agents/` when one repo-local handoff bundle needs to work across Codex, Claude Code, Cursor, GitHub Copilot, Gemini Code Assist, local agents, vendors, and humans without creating official adapter claims.
8. `/en-us/guides/project-handoff-context-budget/` when handoff files are accumulating old reports, chat history, roadmap detail, or pre-slim snapshots that should move to cold memory with transfer evidence.
8. `/en-us/specification/agent-file-handoff/` for chat-start dropped-file intake and review boundaries.
9. `/en-us/specification/agents-md/` for deeper `.uai` linking and record-shape details.
10. `/en-us/reports/`, `/en-us/reports/llm-wiki-vs-uaix-project-handoff/`, `/en-us/reports/llm-wiki-and-uaix-project-handoff/`, and `/en-us/reports/refining-uai-protocol-agent-communication/` for the public report trail.
11. `/en-us/specification/uai-1/`, `/en-us/schemas/`, `/en-us/registry/`, and `/en-us/examples/` for the current UAI-1 contract.
12. `/en-us/tools/validator/`, `/en-us/tools/adoption-kit/`, and `/en-us/tools/conformance-pack/` when the work needs evidence that can travel.
13. `/en-us/roadmap/` and `/en-us/governance/changelog/` before making current-support or future-tooling claims; the roadmap now carries a today-focus path, roadmap work documentation ledger, current work queue, evidence promotion gates, and support-claim checks for moving future work into support.

## Progressive Navigation

If you do not need the full doc stack up front, use `docs/navigation/README.md` for topic-based traversal.

That helper layer points back to `AGENTS.md`, `README.md`, and `docs/current-reference.md` so readers can move through one topic at a time without losing the canonical entry points.

## Current Project Truth

- This is a local WordPress Studio site.
- UAIX.org is the public standards and publication site for UAI and the source of truth for UAI-1.
- UAIX.org owns the official UAI-1 standards surface and official UAIX package guidance. Current official .NET package identity lives on `/en-us/implementations/dotnet-nuget/` as the `UAIX.UAI`, `UAIX.UAI.Abstractions`, `UAIX.UAI.Memory`, `UAIX.UAI.Build`, `UAIX.AdaptiveInteroperability`, `UAIX.Talisman.AgentClient`, and `UAIX.Talisman.EcosystemManager` NuGet package family. Protocol5.com must not be treated as UAI-1 standards authority or as the current official UAIX .NET package identity.
- AIWikis.org is the dogfood implementation and cold-memory archive for large UAIX source notes and processed handoff material. It does not replace UAIX.org as UAI-1 authority or public support evidence.
- The active public theme is `uaix-authority-theme`.
- `uaix-theme` is still packaged and smoke-tested as installable, but it is not the current public launch surface.
- The public site uses clean, descriptive, locale-prefixed paths under `/en-us/...`.

Why This File Exists

This is a memory-system evidence file from uaix.org. 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 memory-system evidence. It records source history, archive transfer, intake disposition, or another piece of provenance that should be retrievable without becoming an unsupported public claim.

Structure

The file is structured around these visible headings: 3.117.0 - Agent Capability Alignment; 3.114.0 - Agent Capability Alignment; 3.65.0 - Agent Capability Alignment; 2026-06-10 - Memory Maintenance And Protected Artifact Boundary; 3.67.0 - Launch-Baseline Required File Set; 3.66.0 - API Reference And Discovery Hotfix; 3.65.0 - Workspace Version Authority Alignment; 3.63.0 - Required Anchor Draft. 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

Provenance And History

  • Current observation: 2026-06-22T01:56:21.9510185Z
  • Source origin: current-source-workspace
  • Retrieval method: local-source-workspace
  • Duplicate group: sfg-702 (primary)
  • Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "UAIX Workspace",
    "source_site":  "uaix.org",
    "source_url":  "https://uaix.org/",
    "canonical_url":  "https://aiwikis.org/uaix/files/readme-md-939d1d36/",
    "source_reference":  "README.md",
    "file_type":  "md",
    "content_category":  "memory-file",
    "content_hash":  "sha256:939d1d362728b493a36e235a4f5c48700201fe10d4a23dce9e363a2348f00119",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-06-21T20:28:13.4833227Z",
    "import_status":  "changed",
    "duplicate_group_id":  "sfg-702",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-06-22T01:56:21.9510185Z"
}

Next Useful Routes

  • Start Here A task-first reading path for AIWikis.org, separating newcomer learning, source-memory lookup, maintainer workflow, and AI-agent retrieval.
  • Topic Index A tag-oriented index for LLM Wiki, AI memory, UAI, source governance, crawling, and retrieval topics.
  • Source Map AIWikis source-governed page for durable AI memory, evidence routing, and agent-readable retrieval.
  • UAIX.org UAIX.org source-system overview for transparent AIWikis memory demonstration.
  • UAIX.org Source Memory Guide AIWikis source-governed page for durable AI memory, evidence routing, and agent-readable retrieval.
  • UAIX.org Files Site-scoped current-source file index for UAIX.org.