Skip to content
aiWikis.org

UAIX Project Context

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

Metadata

FieldValue
Source siteaiwikis.org
Source URLhttps://aiwikis.org/
Canonical AIWikis URLhttps://aiwikis.org/files/aiwikis/raw-system-archives-uaix-recent-work-sweep-2026-05-03-uai-context-uai-b546c9b7/
Source referenceraw/system-archives/uaix/recent-work-sweep/2026-05-03/.uai/context.uai
File typeuai
Content categoryuai-system
Last fetched2026-05-03T02:48:13.1276041Z
Last changed2026-05-02T23:56:01.9803905Z
Content hashsha256:b546c9b7a397226ecf10e61f299c87e0a48816209a2177f5b5550b05f3fc2229
Import statusunchanged
Raw source layerdata/sources/aiwikis/raw-system-archives-uaix-recent-work-sweep-2026-05-03-uai-context-uai-b546c9b7a397.uai
Normalized source layerdata/normalized/aiwikis/raw-system-archives-uaix-recent-work-sweep-2026-05-03-uai-context-uai-b546c9b7a397.txt

Current File Content

Structure Preview

  • UAIX Project Context
  • What This Is
  • Primary Goal
  • Who This Repo Serves
  • Current Public Truth
  • What A New AI Should Understand Quickly
  • Success Criteria For Changes

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.

---
uaix: "1.0"
type: context
title: "UAIX Project Context"
created: "2026-04-25"
updated: "2026-05-02"
status: active
author: "UAIX maintainers"
version: 27
---

# UAIX Project Context

## What This Is

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

UAIX is the public standards and publication site for UAI. UAI-1 is the current public exchange contract and evidence layer published there.

This repo contains the active public theme, supporting plugins, canonical project docs, release scripts, and the local Studio runtime used to test changes before publishing packages.

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

Protocol5.com is not the UAI-1 standards site or source of truth. It may provide .NET plugins and NuGet packages and should link back to UAIX.org for the canonical UAI-1 specification, schemas, registry, validator, roadmap, governance, and support-boundary pages.

## Primary Goal

Keep the public UAIX record clear, auditable, easy to navigate, and honest about what is and is not currently supported.

For current work, a major goal is to make AI Memory, the AI Memory Package Wizard, Project Handoff, `AGENTS.md`, root `readme.human`, and `.uai` files practical enough that a fresh AI can onboard from repository context alone without private chat history and a human can understand what the AI sees before steering it.

The repo-local handoff path is deliberately specialized and local-first: `AGENTS.md` is the front door, `readme.human` is the human briefing, typed `.uai` files carry detailed context, and `agent-file-handoff/` carries dropped-file intake when relevant. Direct pointing to UAIX.org pages is useful for bootstrap, refresh, and public-source verification, but recurring Codex/agent work should prefer local, versioned, auditable Markdown, JSON, YAML, and script artifacts over repeated live URL reading.

The repo also includes `.agents/skills/uaix-handoff/` as a Codex-local workflow aid for repeating the handoff load, intake review, and targeted-check sequence. The skill is local workflow documentation, not a public UAIX SDK, CLI, official adapter, certification, endorsement, or UAI-1 conformance surface.

The repo now also includes thin tool-specific pointers for Claude Code, Cursor, GitHub Copilot, and Gemini Code Assist. They point back to `AGENTS.md`, `readme.human`, and `.uai` records; they are not separate project-truth files and do not create official UAIX adapter support.

That now includes chat-start file handoff: when a new AI reads `AGENTS.md` and the loaded `.uai` files, it must check `agent-file-handoff/Content/` for candidate public/editorial material and `agent-file-handoff/Improvement/` for audits, QA findings, SEO reports, bug notes, and site-fix work; refresh `.uai/intake-index.uai`; and immediately inspect and disposition any `needs-agent-review` files before unrelated broad work. Already-dispositioned files belong in `agent-file-handoff/Archive/`, which is ignored by routine AI intake unless a human explicitly names an archived file or moves it back into an active bucket. `scripts/Invoke-UaiFileIntake.ps1` is the local helper for that scan. The pattern intentionally avoids watchers, daemons, queue folders, manifests, always-on background services, and per-folder README instructions so it can work in any language or environment with durable behavior kept in `AGENTS.md` and `.uai` files.

The repo now uses a hot/cold memory split. UAIX hot context is the compact local handoff bundle loaded every session. AIWikis cold memory preserves bulky internal research, proposal history, older roadmap material, and pre-slim handoff snapshots. The 2026-05-01 transfer evidence lives in AIWikis `raw/system-archives/2026-05-01-uaix-internal-memory-reorg.json`; use it only when a task needs original wording or historical provenance.

## Who This Repo Serves

- UAIX maintainers updating the public standards site
- AI assistants working inside the repo
- Implementers evaluating UAI-1 and its public evidence surface
- Reviewers checking support claims, launch readiness, and release discipline

## Current Public Truth

- The active public theme is `uaix-authority-theme`.
- UAIX.org is the authoritative public site for UAI and UAI-1.
- `uiax.org` and `www.uiax.org` are typo-domain aliases that redirect anonymous public traffic to `https://uaix.org` while preserving path/query, excluding `/wp-admin/`, `/wp-login.php`, and logged-in WordPress sessions.
- Protocol5.com is a .NET/NuGet implementation distribution and backlink surface, not a standards authority.
- Public production routes are clean locale-prefixed routes under `/en-us/...`.
- Supported public languages are `en-US` and `zh-CN`; other locale inventory records are disabled until full content, metadata, hreflang, sitemap, and rendered-text audit coverage exists.
- Root `robots.txt`, `sitemap.xml`, `sitemap.html`, `/.well-known/uaix.json`, and `/.well-known/uai.json` are part of the public discovery surface.
- `/en-us/ai-memory/` is the canonical public AI Memory page. It explains durable AI project memory, defines Project Handoff as the transfer subtype, provides a supported configuration chooser, describes when an optional LLM Wiki can help deep internal documentation, and publishes starter ZIPs generated on demand from canonical templates, generated manifests, and the same rendered samples shown on the page. `/AI_Memory` redirects to the canonical locale-prefixed route as the requested non-canonical entry alias.
- `/en-us/ai-memory/llm-wiki/` is the public guide for using UAI packages with an LLM Wiki. It must stay clear that LLM Wiki is not required by UAI specs or standards; it is optional support for tailoring package strategy when a project already uses or deliberately chooses deeper wiki memory.
- `/en-us/specification/project-handoff/` now positions Project Handoff as portable project memory for humans and AI agents, not an agent runtime or OpenAI replacement. The public line to preserve is: OpenAI runs the agents; Project Handoff preserves the project memory.
- `/en-us/guides/agentic-harnesses-uai/` is the public guide for agentic harness strategy and UAI fit. Preserve the split: harnesses execute; MCP/A2A/runtime tools coordinate and trace behavior; UAI preserves reviewed portable evidence, AI Memory, Project Handoff, conformance material, and support boundaries.
- `/en-us/guides/project-handoff-openai/` is the public guide for using UAIX Project Handoff with OpenAI Agents and Codex. It explains what OpenAI handles, what Project Handoff handles, the minimum repo bundle, example `AGENTS.md`, example `.uai/constraints.uai`, example `.uai/test-plan.uai`, seeding an agent run, writing accepted results back, what not to put in the handoff, and the human approval checklist.
- `/en-us/guides/project-handoff-coding-agents/` is the public guide for using one repo-local Project Handoff bundle across Codex, Claude Code, Cursor, GitHub Copilot, Gemini Code Assist, local agents, vendors, and humans while keeping tool-specific files thin and avoiding official adapter, SDK, CLI, certification, conformance, or endorsement claims.
- `/en-us/guides/project-handoff-context-budget/` is the public guide for keeping `AGENTS.md`, `readme.human`, and `.uai` startup context compact while old research, reports, chats, roadmap history, and pre-slim snapshots live in AIWikis or LLM Wiki cold memory with transfer evidence.
- `/en-us/tools/ai-memory-package-wizard/` is the public UAI AI Memory Package Wizard. It guides one supported starter preset through a six-step flow: preset, basics, operations, protocols, receiver, and review/export. The page now has direct setup paths for base UAI package planning, Agent File Handoff, LLM Wiki, and File Handoff plus LLM Wiki; page-level validation; local browser draft restore; sensitive/high-risk review gate auto-enabling; a dedicated review/export step; package model JSON; manifest overlay JSON; generated exact-root `UAI_MEMORY_SYSTEM_PROFILE.md`, `UAI_MEMORY_RECEIVER_BRIEF.md`, `UAI_MEMORY_STARTUP_PACKET.md`, and optional `AGENT_FILE_HANDOFF_PLAN.md` files; a copy-paste file deck; operating strategy choices for collaboration model, UAI-only versus UAI plus Wiki memory architecture, unit/integration testing, test timing, deployment, code review, release gates, source-authority policy, memory-update policy, evidence ledger path, conflict-resolution policy, change-risk level, rollback strategy; an optional generated exact-root `LLM_WIKI_MEMORY_PLAN.md` file for projects that also use LLM Wiki long-memory; wiki strategy/topology fields; steward/source/evidence-log metadata; a readiness checklist; optimized human-wizard and visitor-AI digest entry artwork; a compact visitor-AI digest JSON generated from the same canonical wizard payload and bundle registry; and the matching canonical starter ZIP download without claiming hosted upload/import validation, automatic repository writes, automatic LLM Wiki sync, SDK, CLI, certification, endorsement, or WordPress admin installation.
- `/en-us/specification/standards-fit/` is the public fit-and-boundary page for UAI-1 beside MCP, A2A, OpenAPI, JSON Schema, DID/VC, Trace Context, compact transfer, and current bridge evidence. It now carries the quick chooser and UAI-1 vs MCP/A2A decision path without claiming runtime replacement, formal bridge profiles, SDKs, CLIs, certification, endorsement, or compliance support.
- `/en-us/guides/` and `/en-us/specification/standards-fit/` now make the agentic-system architecture path explicit: runtime harnesses run the work, MCP connects tools, A2A coordinates agents, observability systems trace behavior, and UAIX records the portable evidence and handoff packet that must survive the run.
- `/en-us/roadmap/` and `/wp-json/uaix/v1/roadmap` now expose a today-focus path, roadmap work documentation ledger, current work queue, evidence promotion gates, and support-claim checks for reader orientation, first proof runs, AI Memory package work, future-agent pickup, source-lead promotion, agentic-system evidence planning, deployment cleanup, wizard serializer parity, local validation/redaction lint, trace-to-handoff fixtures, reference-adapter evaluation, AI Memory package scope, adapter/runtime scope, and conformance wording while keeping unsupported items out of current-support language until public proof exists.
- Public handoff and agentic-system pages include Project Handoff, the Agentic Harness Strategies and UAI guide, the OpenAI/Codex Project Handoff guide, the coding-agents Project Handoff guide, the Project Handoff Context Budget guide, Agent File Handoff, the AGENTS.md `.uai` linking specification, the Reports index, the LLM Wiki comparison reports, and the refining report.
- The public relationship audit keeps the sibling-site roles explicit: AIWikis.org is dogfood implementation and archive-memory consumer, LLMWikis.org is the handbook and explainer layer, and UAIX.org remains the canonical UAI-1 authority.
- AIWikis.org also carries cold-memory source archives for slimmed UAIX internal docs and pre-slim handoff snapshots. AIWikis memory is provenance, not active UAIX support evidence until promoted back into UAIX source state.
- The repo itself now uses root `AGENTS.md`, root `readme.human`, plus `.uai/` files as the live handoff example, and `agent-file-handoff/` as the live AGENTS.md-triggered intake and archive example.
- `.uai/handoff-pattern.uai` is the repo-local explanation of how to adapt public website, README, release, and operations instructions into a portable handoff bundle.

## What A New AI Should Understand Quickly

After reading `AGENTS.md` and the loaded `.uai` files, a new AI should be able to answer:

1. What UAIX is and what UAI-1 is.
2. Which theme and plugins define the current public surface.
3. Which docs are canonical.
4. Which routes and claims are public today.
5. Which constraints must not be violated.
6. Which scripts verify packaging, routing, and launch readiness.
7. What work is current, planned, or still outside support boundaries.
8. Which public routes explain AI Memory, the Package Wizard, Project Handoff, UAI-1, validation evidence, and support boundaries.
9. What it must report in its first response before broad edits.
10. Whether any newly dropped files require review, what each file contains, and how each one was dispositioned before broad work.
11. What the human-facing briefing says people should make explicit before steering the system.

## Success Criteria For Changes

- Public pages, machine-readable artifacts, and canonical docs stay aligned.
- Support claims stay scoped to what the public site actually publishes.
- AI handoff guidance remains easy for a zero-context reader to follow.
- Release and QA scripts remain the source of verification rather than ad hoc guesses.

Why This File Exists

This is a UAI AI Memory handoff file from aiwikis.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 .uai file is a compact context packet. It keeps one kind of durable project truth separate from the rest of the archive so an agent can load the topic it needs without pulling the whole project history into prompt context.

Structure

The file is structured around these visible headings: UAIX Project Context; What This Is; Primary Goal; Who This Repo Serves; Current Public Truth; What A New AI Should Understand Quickly; Success Criteria For Changes. 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-05-03T02:48:13.1276041Z
  • Source origin: current-source-workspace
  • Retrieval method: local-source-workspace
  • Duplicate group: sfg-344 (primary)
  • Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "UAIX Project Context",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/files/aiwikis/raw-system-archives-uaix-recent-work-sweep-2026-05-03-uai-context-uai-b546c9b7/",
    "source_reference":  "raw/system-archives/uaix/recent-work-sweep/2026-05-03/.uai/context.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:b546c9b7a397226ecf10e61f299c87e0a48816209a2177f5b5550b05f3fc2229",
    "last_fetched":  "2026-05-03T02:48:13.1276041Z",
    "last_changed":  "2026-05-02T23:56:01.9803905Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-344",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-05-03T02:48:13.1276041Z"
}