UAIX Project Handoff And Canonical AI Memory Assessment

UAIX currently publishes **two related but distinct layers**. The first is **UAI-1**, a formal, machine-readable exchange standard with published schemas, registry records, examples, transport bindings, trust channels...

Metadata

Field	Value
Source site	uaix.org
Source URL	https://uaix.org/
Canonical AIWikis URL	https://aiwikis.org/uaix/files/raw-system-archives-uaix-agent-file-handoff-retired-source-archive-2026-4d1491c2/
Source reference	raw/system-archives/uaix/agent-file-handoff/retired-source-archive-2026-06-13/2026-05-06/Improvement/canonical-ai-memory/UAIX Project Handoff and Canonical AI Memory Assessment.md
File type	md
Content category	memory-file
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-05-06T16:24:34.4988997Z
Content hash	sha256:4d1491c2d9e31951b9bdffdfb4ea5e263d799952c490c2cb0b83e772dda33861
Import status	unchanged
Raw source layer	data/sources/uaix/raw-system-archives-uaix-agent-file-handoff-retired-source-archive-2026-06-13-2026-05-06-improve-4d1491c2d9e3.md
Normalized source layer	data/normalized/uaix/raw-system-archives-uaix-agent-file-handoff-retired-source-archive-2026-06-13-2026-05-06-improve-4d1491c2d9e3.txt

Current File Content

Structure Preview

• UAIX Project Handoff and Canonical AI Memory Assessment
• Executive summary
• What UAIX publishes today
• Handoff architecture and workflow
• Data models, APIs, and metadata
• Security, privacy, versioning, and governance
• Interoperability and standards comparison
• Recommendations and implementation starter kit
• Crawled pages and limitations

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: 40178
• Preview characters: 11941

# UAIX Project Handoff and Canonical AI Memory Assessment

## Executive summary

UAIX currently publishes **two related but distinct layers**. The first is **UAI-1**, a formal, machine-readable exchange standard with published schemas, registry records, examples, transport bindings, trust channels, validator guidance, conformance levels, discovery routes, and an advertised OpenAPI document. The second is **AI Memory / Project Handoff**, which is a **repo-local durable memory and transfer system** built from `AGENTS.md`, `readme.human`, `.uai` records, generated starter bundles, and wizard-produced overlays and briefs. In other words, UAI-1 is the interoperable message contract; Project Handoff is the operational memory packet that agent runtimes are meant to load before work and update after work. citeturn17view0turn17view2turn16view1turn9view5turn7view1turn7view3turn39view3

The strongest current UAIX artifact for “canonical AI Memory” is **not one monolithic specification**. Instead, it is a **distributed operating surface** made up of the AI Memory framing, the Project Handoff specification, the AI Memory Package Wizard, Agent File Handoff, the Context Budget guide, and supporting governance pages. The practical conclusion is that **Project Handoff is the clearest current canonical operating form** for durable repository memory, while the AI Memory Package Wizard is the clearest current canonical generator/planning surface for those bundles. citeturn7view3turn25view0turn25view2turn31view1turn31view2

UAIX’s biggest strengths are its **explicit trust boundary language**, its separation of **runtime execution** from **durable project memory**, its use of **reviewable local files instead of private chat memory**, its published **conformance and evidence model**, and its insistence that support claims must remain tied to named public records and release evidence. citeturn7view1turn7view8turn7view9turn23view2turn13view2turn27view2turn31view0

Its biggest gaps are equally clear. I did **not** find a single formal public schema for the **Project Handoff bundle itself**; I found **template- and manifest-driven bundles**, plus draft/proposal material. I also found an internal inconsistency in local memory record syntax: some `.uai` examples use front matter with `uai: "1.0"`, while Agent File Handoff templates use `uaix: "1.0"`, and the separate AGENTS.md linking report proposes `.uai` as JSON/YAML-style informational files. That means the **message layer is more formally specified than the memory layer** today. citeturn7view4turn7view10turn23view4turn23view5turn21view0turn21view1

Interoperability is strongest today with **Git-centered, repo-local workflows** and with **runtime-neutral agent orchestration**. It is conceptually aligned with OpenAI, MCP, and A2A, and practical across Codex, Claude Code, Cursor, Copilot, and Gemini Code Assist, but UAIX explicitly warns readers **not** to treat these patterns as official adapters, SDKs, CLIs, certifications, or vendor endorsements. I found **no current official Jira, Notion, or Slack adapters** in the published implementation tracks or roadmap. citeturn40view0turn40view2turn39view3turn27view0turn31view1turn31view3

For adoption, the best current strategy is pragmatic: use **Project Handoff** as a **portable repo-local memory discipline**, use **UAI-1** only when you need **portable message exchange and validator-backed evidence**, and treat broader package automation, managed package records, adapters, sync, and official tool integrations as **planned or research-track** rather than current support. citeturn7view1turn17view3turn31view1turn31view3

## What UAIX publishes today

UAIX’s own discovery surface reports a current **UAI-1** release with version **1.0**, release date **2026-04-22**, and a public machine surface that includes **6 schemas**, **6 registry entries**, **6 examples**, **2 transport bindings**, **5 trust channels**, **4 conformance levels**, **11 error codes**, plus discovery, validation, adoption-kit, mock-exchange, OpenAPI, conformance-pack, roadmap, and status routes. It also publishes a public page map covering AI Memory, Project Handoff, AGENTS.md specification, Agent File Handoff, Schemas, Registry, Examples, Implementations, Tools, Governance, Roadmap, and Reports. citeturn11view0turn12view0

Analytically, the site breaks into four functional zones: a **memory/handoff zone**, a **formal protocol zone**, a **tooling/evidence zone**, and a **governance/release zone**. That separation is a genuine design strength because it keeps “portable context” separate from “portable message exchange,” and both separate from “public support claims.” citeturn7view1turn17view2turn27view0turn28view0

The following site map condenses the pages and machine surfaces that matter most for AI Memory and Project Handoff. It is synthesized from the discovery JSON and the crawled canonical pages. citeturn11view0turn12view0

```mermaid
graph TD
    A[UAIX Home] --> B[AI Memory]
    A --> C[Project Handoff]
    A --> D[Agent File Handoff]
    A --> E[AGENTS.md Spec]
    A --> F[Context Budget Guide]
    A --> G[OpenAI Guide]
    A --> H[Coding Agents Guide]

    A --> I[UAI-1]
    I --> J[Schemas]
    I --> K[Registry]
    I --> L[Examples]
    I --> M[Standards Fit]

    A --> N[API Reference]
    N --> O[/catalog]
    N --> P[/discovery]
    N --> Q[/schemas]
    N --> R[/registry]
    N --> S[/field-registry]
    N --> T[/transport-bindings]
    N --> U[/trust-channels]
    N --> V[/conformance-levels]
    N --> W[/error-registry]
    N --> X[/validate]
    N --> Y[/mock-exchange]
    N --> Z[/openapi.json]
    N --> AA[/conformance-pack]

    A --> AB[AI Memory Package Wizard]
    A --> AC[Implementations]
    AC --> AD[WordPress Track]
    AC --> AE[.NET Bridge Track]

    A --> AF[Governance]
    AF --> AG[Policy and Security]
    AF --> AH[Privacy and Data]
    AF --> AI[Changelog]
    AF --> AJ[Roadmap]
```

A high-confidence conclusion from the crawl is that **canonical AI Memory on UAIX is operationally real but formally distributed**. The site publishes canonical templates, generated manifests, bundle IDs, starter ZIPs, and a bundle registry-driven wizard, but not a single public, normative “AI Memory core schema” equivalent to the formal schemas that UAI-1 publishes for message exchange. citeturn7view4turn25view0turn25view2turn31view2

## Handoff architecture and workflow

UAIX repeatedly states that **agent runtimes execute**, while **Project Handoff preserves durable project memory**. The memory system lives “one layer earlier and one layer later” than runtime execution: it tells a runtime what durable memory to load before work starts, and where accepted truth should be written back when work finishes. That architectural stance is consistent across the Project Handoff spec and the OpenAI-oriented guide. citeturn7view1turn6view6turn39view0turn39view3

The **minimum Project Handoff bundle** is straightforward: a project root with `AGENTS.md`, `readme.human`, and `.uai/context.uai`, `.uai/stack.uai`, `.uai/constraints.uai`, `.uai/progress.uai`, and `.uai/test-plan.uai`. UAIX presents `AGENTS.md` as the “durable front door,” `readme.human` as the human briefing, and the `.uai` files as typed records for project context, stack, constraints, progress, and testing. citeturn7view2

The **extended Project Handoff starter** is much richer. UAIX publishes a 25-file starter ZIP generated from “visible canonical files,” including a `UAI_MEMORY_MANIFEST.json`, root narrative files such as `README.md`, `PROJECT_OVERVIEW.md`, `CURRENT_STATE.md`, `DECISIONS.md`, `OPEN_QUESTIONS.md`, `NEXT_ACTIONS.md`, `RISKS_AND_CONSTRAINTS.md`, `CONTACTS_AND_OWNERS.md`, `AGENT_INSTRUCTIONS.md`, `CHANGELOG.md`, `DEPLOYMENT_MEMORY_AND_TEST_REPORT.md`, and local `.uai` records for context, constraints, memory, stack, architecture, progress, operations, test plan, style, and decisions, plus `HANDOFF_BRIEF.md`. citeturn7view4turn7view5turn7view6

The startup reading order is explicit. A receiving AI is told to read `AGENTS.md`, then `readme.human`, then load the files in the “Loaded Context” list via `@uai[]`, report contradictions or missing context, read summary/current-state/next-step sections, summarize understanding in 3–5 bullets, and confirm hard constraints. That is a stronger handoff discipline than a loose README-only approach, because it forces **early constraint acknowledgment and verification planning**. citeturn6view5turn7view8

The following flow diagram summarizes the operating loop UAIX describes. It combines the Project Handoff page, the OpenAI guide, the context-budget guidance, and the Agent File Handoff extension. citeturn39view3turn23view0turn41view1

```mermaid
flowchart LR
    H[Human or prior agent] --> W[AI Memory Package Wizard or hand-edited bundle]
    W --> PH[Project Handoff bundle in repo]
    PH --> A1[AGENTS.md]
    PH --> A2[readme.human]
    PH --> A3[Loaded .uai records]

    A1 --> R[Agent runtime]
    A2 --> R
    A3 --> R

    F[Optional Agent File Handoff buckets] --> R
    R --> C[Checks, traces, PRs, targeted edits]
    C --> U[Write back accepted truth]
    U --> P1[progress.uai]
    U --> P2[decisions.uai]
    U --> P3[deployment and test report]
    U --> P4[handoff brief / next actions]

    U --> CM[Cold memory or LLM Wiki pointer only after review]
```

A particularly important extension is **Agent File Handoff**, which UAIX positions as a small auditable inbox for “loose files supplied by humans, other AI systems, exports, and adjacent tools.” Its rule is simple: a dropped file is not part of handoff until it is **visible, reviewed, and dispositioned**. The directory contract uses `agent-file-handoff/Content/`, `agent-file-handoff/Improvement/`, `agent-file-handoff/Archive/`, plus `.uai/file-handoff.uai`, `.uai/intake-index.uai`, and loader instructions in `AGENTS.md`. citeturn23view0turn23view1turn22view7

This structure becomes more rigorous when paired with UAIX’s **Context Budget** guidance. That guide distinguishes **hot Project Handoff** from **cold memory**, saying hot context should carry current truth and constraints, while long research, old chats, raw audits, and superseded notes should move to cold memory with source path, final path, checksum, actor, timestamp, summary, and disposition. In practical terms, UAIX is trying to prevent “AI Memory” from turning into an unbounded archive. citeturn41view1turn41view5

The table below condenses the published bundle archetypes and templates. It is synthesized from Project Handoff, Agent File Handoff, and the AI Memory Package Wizard. citeturn7view2turn7view4turn23view4turn25view2

| Artifact or template | Format | Operational role | Current status in crawl |
|---|---|---|---|
| `AGENTS.md` | Markdown | Canonical front door; load order, current state, rules, required first response | Current, central |
| `readme.human` | Markdown | Human-facing briefing from AI perspective | Current, recommended |
| `.uai/context.uai` | Front matter + prose | Purpose, audience, success criteria | Current |
| `.uai/constraints.uai` | Front matter + prose | Red lines, secrets policy, destructive-operation limits | Current |
| `.uai/stack.uai` | Front matter + prose | Languages, frameworks, commands, runtime assumptions | Current |
| `.uai/progress.uai` | Front matter + prose | Current focus, blockers, next work | Current |
| `.uai/test-plan.uai` | Front matter + prose | Targeted checks and verification plan | Current |
| `.uai/decisions.uai` | Front matter + prose | Accepted decisions and reversal conditions | Current |
| `HANDOFF_BRIEF.md` | Markdown | Transfer-specific acceptance criteria and risks | Current |
| `DEPLOYMENT_MEMORY_AND_TEST_REPORT.md` | Markdown | Release-bound memory/test evidence | Current |

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: UAIX Project Handoff and Canonical AI Memory Assessment; Executive summary; What UAIX publishes today; Handoff architecture and workflow; Data models, APIs, and metadata; Security, privacy, versioning, and governance; Interoperability and standards comparison; Recommendations and implementation starter kit. 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
• Site file index
• Site report index
• UAI system index
• Source provenance
• Site directory
• Organization reports

Provenance And History

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

Machine-Readable Metadata

{
    "title":  "UAIX Project Handoff And Canonical AI Memory Assessment",
    "source_site":  "uaix.org",
    "source_url":  "https://uaix.org/",
    "canonical_url":  "https://aiwikis.org/uaix/files/raw-system-archives-uaix-agent-file-handoff-retired-source-archive-2026-4d1491c2/",
    "source_reference":  "raw/system-archives/uaix/agent-file-handoff/retired-source-archive-2026-06-13/2026-05-06/Improvement/canonical-ai-memory/UAIX Project Handoff and Canonical AI Memory Assessment.md",
    "file_type":  "md",
    "content_category":  "memory-file",
    "content_hash":  "sha256:4d1491c2d9e31951b9bdffdfb4ea5e263d799952c490c2cb0b83e772dda33861",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-05-06T16:24:34.4988997Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-381",
    "duplicate_role":  "primary",
    "related_files":  [

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