Project Handoff System And Canonical AI Memory (Llmwikis Analysis)

Compared to best practices, LLMWikis’ approach emphasizes structured persistence and governance (drawing on standards like UAI-1 and AGENTS.md) whereas many AI workflows rely on informal notes or RAG. Key differences...

Metadata

Field	Value
Source site	llmwikis.org
Source URL	https://llmwikis.org/
Canonical AIWikis URL	https://aiwikis.org/llmwikis/files/raw-system-archives-llmwikis-agent-file-handoff-retired-source-archive-2-27b64d35/
Source reference	raw/system-archives/llmwikis/agent-file-handoff/retired-source-archive-2026-06-13/2026-05-06/Improvement/canonical-ai-memory/Project Handoff System and Canonical AI Memory UAIX and LLMWikis.md
File type	md
Content category	memory-file
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-05-06T15:19:06.9204821Z
Content hash	sha256:27b64d353726803faa74fed14723cc9381b1d16055242c2b660ee358435e4847
Import status	unchanged
Raw source layer	data/sources/llmwikis/raw-system-archives-llmwikis-agent-file-handoff-retired-source-archive-2026-06-13-2026-05-06-imp-27b64d353726.md
Normalized source layer	data/normalized/llmwikis/raw-system-archives-llmwikis-agent-file-handoff-retired-source-archive-2026-06-13-2026-05-06-imp-27b64d353726.txt

Current File Content

Structure Preview

• Project Handoff System and Canonical AI Memory (LLMWikis Analysis)
• AGENTS.md – Project Handoff Summary

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: 27609
• Preview characters: 11835

# Project Handoff System and Canonical AI Memory (LLMWikis Analysis)

**Executive Summary:** LLMWikis and the UAIX standard define a structured memory architecture to ensure AI agents operate on a durable, audited context instead of opaque chat history.  Under this model, a **durable LLM Wiki** serves as the reviewed, authoritative knowledge base; an **AI Memory** bundle is a compact, portable “working context” for a bounded task; and a **Project Handoff** is a specialized AI Memory packet to transfer responsibility to a new agent or team【1†L44-L47】【12†L41-L49】.  In practice, handoff bundles use files like `AGENTS.md`, `readme.human`, and typed `.uai/` JSON files (e.g. `context.uai`, `stack.uai`, `constraints.uai`, `progress.uai`, `test-plan.uai`) to capture project identity, current state, rules, and next steps【2†L61-L69】【16†L369-L378】.  Agents load these files via explicit references (`@uai[...]`) to assemble a known context, then update progress and decisions back into the bundle.  This contrasts with typical stateless RAG systems or opaque chat memory: AI Memory is **file-based, reviewable, and schema-driven**【21†L236-L244】【23†L1221-L1230】.  Industry sources (e.g. OpenAI’s documentation) show trends toward user-level “memory”, but corporate AI systems often lack standards for project context. UAIX fills this gap with open schemas and a REST API for validation【21†L236-L244】【23†L1221-L1230】.

Compared to best practices, LLMWikis’ approach emphasizes structured persistence and governance (drawing on standards like UAI-1 and AGENTS.md) whereas many AI workflows rely on informal notes or RAG. Key differences include explicit trust boundaries (e.g. excluding secrets or PII【23†L1183-L1190】【16†L413-L419】), human review checkpoints, and versioned manifests for context.  Our analysis finds **gaps** in tool support and standard maturity (UAIX tooling is nascent), **risks** around privacy/leaks if procedures lapse, and operational overhead to maintain the wiki and memory artifacts.  We recommend a staged implementation: establish an LLM Wiki for core knowledge, pilot UAIX-style memory bundles on a pilot project, integrate a validation/CI pipeline, and train stakeholders on review protocols.  Success can be measured by metrics such as reduced context loss in handoffs, audit-complete memory packets for each release, and shorter onboarding times.

**Key Findings:** LLMWikis’ handbook and the UAIX standard converge on a layered memory design. The **LLM Wiki** is a durable internal knowledge base (reviewed pages, indexed content, audit logs)【1†L51-L59】. **AI Memory** (UAIX) is a lightweight context bundle for a task: “project purpose, current state, constraints, decisions, next actions, owners, trust boundaries, maintenance rules, and targeted checks”【21†L236-L244】.  **Project Handoff** is a subtype of AI Memory for transferring work to another actor【1†L44-L47】【12†L53-L58】.

- **Definition (LLMWikis):** “Use LLM Wiki, AI Memory, and Project Handoff as different layers… The LLM Wiki is the durable reviewed base. AI Memory is the compact portable operating context. Project Handoff is the transfer packet that lets a person, team, vendor, or agent take over work.”【1†L44-L47】.
- **Definition (UAIX):** “UAI AI Memory is a lightweight, portable, file-based standard for durable context. It gives humans and AI agents a reviewable packet of project memory instead of relying on private chat history…”【21†L236-L244】.  “Project Handoff: Portable project memory, governance, and review context for agent runtimes, humans, vendors, teams, and future sessions.”【14†L62-L65】.
- **Project Handoff Components:** The **minimum handoff bundle** (per UAIX) is a directory:
  ```
  my-project/
    AGENTS.md
    readme.human
    .uai/
      context.uai
      stack.uai
      constraints.uai
      progress.uai
      test-plan.uai  (optional if needed)
      [optionally: architecture.uai, decisions.uai, style.uai, etc.]
  ```
  - `AGENTS.md` – a durable “front door” summary: current state, loaded context list, next steps, history, open questions, and instructions for the first response【2†L61-L69】【16†L369-L378】.
  - `readme.human` – a human-readable briefing: what humans should know to supervise the AI, unsafe assumptions, and clarifications【2†L61-L69】【16†L369-L378】.
  - `.uai/` files – typed JSON/YAML context segments: e.g. `context.uai` (purpose, audience, success criteria), `stack.uai` (tech stack, runtime settings), `constraints.uai` (hard rules like “no destructive ops”), `progress.uai` (current tasks, blockers, next actions), `test-plan.uai` (checks and gates), etc【2†L61-L69】【16†L369-L378】.
  - **References:** In `AGENTS.md` or other files, explicit `@uai[...]: path` links indicate which `.uai` files or wiki pages to load【16†L369-L378】.
- **Workflow:** Upon handoff, an AI (or human) agent **loads** the bundle: reads `AGENTS.md`, `readme.human`, and required `.uai` files into its context (via agent API or LLM prompt injection)【16†L389-L398】.  It then **performs work** (e.g. code or content edits) within those constraints. After execution, the agent **updates** the bundle: appending traces to `progress.uai`, logging decisions to `decisions.uai`, and writing any new findings or artifacts back into the wiki or `.uai` files.  Key governance steps (e.g. tests, human approvals) are explicitly triggered by `constraints.uai` and `test-plan.uai`【16†L389-L398】【16†L427-L439】.
  - **First Response Check:** The next agent is expected to summarize the project and confirm that it has loaded context correctly before editing. Specifically, it should name the project identity, public surface, received files, hard constraints, intended edits, and verification plan【2†L88-L96】. This “initial sanity check” catches stale context or authority drift before work begins.
  - **File Intake:** Loose files (notes, exports, images) are handled via the **Agent File Handoff** pattern. All new files are placed into `agent-file-handoff/Content/` (candidate public content) or `/Improvement/` (internal notes) and must be *inspected, summarized, and dispositioned* by the agent (mark as “handled”, “needs-human-review”, “ignore”, etc) before proceeding【2†L106-L114】.  This ensures dropped files do not silently influence decisions or leak sensitive data. Already-handled files move to an `Archive/` bucket and are ignored unless reactivated【2†L106-L114】.

- **LLMWikis Workflow Rules:** The LLMWiki handbook prescribes “layered” rules:
  1. **Routing Rule:** Keep **durable knowledge** (policies, architecture, decisions) in the wiki; keep **active context** (current facts, constraints, state) in AI Memory; keep **transfer context** (local state to resume work) in Project Handoff【1†L66-L74】. Archive or “cold store” old details separately.
  2. **Promotion:** Only reviewed facts move from raw notes (or chat transcripts) into the wiki or memory. A reviewed claim becomes durable only after checks【1†L80-L88】. Conversely, avoid dumping raw or unverified content into AI Memory.
  3. **Separation:** “Do not blur the layers” – wiki pages are **not** raw AI dumps, AI Memory is **not** the full archive, and handoff is **not** automatic publication【1†L94-L99】. Agents must respect permission and evidence boundaries.

- **LLMWikis Templates:** In building an LLMWiki, standard file templates are provided (e.g. starter bundle with `index.md`, `log.md`, and trust labels).  Metadata frontmatter (YAML) is recommended on every wiki page, with fields like `title`, `owner`, `status`, `last_reviewed`, `sensitivity`, and `agent_use`【26†L45-L54】【26†L64-L73】.  These labels ensure pages have clear scope, trust level, and usage rules.  For example, `sensitivity: internal` or `agent_use: allowed-with-citation` control what an AI agent may do.

- **Canonical Schemas:** The UAIX UAI-1 standard defines JSON schemas for the `.uai` files (see UAIX **Schemas**).  Memory bundles include a `UAI_MEMORY_MANIFEST.json` (see code example【16†L498-L510】) listing the bundle ID, name, description, intended use, lifecycle, and fingerprints. Each `.uai` file has a typed profile (e.g. `project-context`, `project-stack`, etc) with structured fields.  These schemas allow automated validation via the UAIX Validator API【11†L73-L81】【33†L163-L171】.

**AI Memory (UAIX) Data & Integration:** AI Memory bundles are purely **file-based** (typically Git repositories or zip packages) containing markdown/JSON.  Agents ingest them by loading the manifest, then each required file (via local filesystem or URL). UAIX provides a REST API for *discovery* and *validation* of memory bundles (e.g. `/wp-json/uaix/v1/validate`【33†L123-L131】) and a “Package Wizard” UI to generate starter bundles from presets.  Integration patterns include:

- **Agent Runtime Compatibility:** UAIX is explicitly “OpenAI-compatible by design”【16†L389-L398】. For instance, `AGENTS.md` acts as the system prompt for Codex or ChatGPT, and `@uai[...]` links point to context files to include.  A UAIX *OpenAI adapter* (planned) could automate converting the bundle into API calls with system prompts, user messages, and function calls.
- **Verification:** Every handoff specifies a **verification plan**【16†L427-L439】: targeted tests or lint checks to prove claimed changes. Agents report evidence back into the memory (e.g. logs in `progress.uai`). Automated CI jobs can run these validators before a handoff is approved.
- **Storage & Versioning:** Bundles live in source control (e.g. Git). Each update (task progress or new facts) is a commit. “Cold” history beyond the current context is archived separately (e.g. wiki or a “cold memory” store). Bundles include checksums (fingerprints in the manifest【16†L498-L510】) so changes are auditable. History of bundle changes is tracked in `CHANGELOG.md`.

**Privacy, Security, and Governance:** Both LLMWikis and UAIX emphasize trust boundaries. AI Memory **must not** include secrets, credentials, private keys, or sensitive personal data unless explicitly sanctioned【23†L1183-L1191】【16†L413-L419】.  For example, UAIX advises “Remove secrets, credentials, private keys, tokens, raw customer data… unless the recipient, storage boundary, and review process are explicit”【16†L413-L419】. Memory bundles should be sanitized and access-controlled. LLMWiki metadata (e.g. `sensitivity`, `agent_use`) further restricts how agents use the information【26†L64-L73】.  Human review gates are enforced: any destructive ops, deployments, or external-facing changes require explicit human approval【16†L409-L418】.  When exporting memory externally (e.g. a vendor handoff), *external-handoff* packets (a variant configuration) are heavily redacted【21†L359-L366】.

**Mapping the Canonical AI Memory Concept:** Summarizing UAIX’s vision: AI Memory is not a full knowledge base but a **task-specific snapshot**【21†L236-L244】. It answers “what the next actor needs to know right now.” Its schema covers project overview (`context.uai`), stack/environment (`stack.uai`), hard rules (`constraints.uai`), current state (`progress.uai`), test plan (`test-plan.uai`), and optional others (style, decisions, etc)【2†L67-L75】【16†L369-L378】. Bundles are *versioned* (via manifest fingerprint and commit history) and *retrieved* by agents through the file system or UAIX APIs. Integration patterns include:
- **Storage:** In a VCS or package registry; memory can be zipped for handoff. Bundles may be uploaded to a registry or served via API (UAIX’s `/catalog`, `/discovery` routes【33†L119-L127】).
- **Retrieval:** Agents or systems load memory by reading files listed in `@uai` references or by calling the UAIX API to fetch bundle contents. The UAIX **Validator** and **Adoption Kit** APIs allow tools to automatically fetch and check bundles against the public schemas【33†L119-L127】.

Why This File Exists

This is a memory-system evidence file from llmwikis.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: Project Handoff System and Canonical AI Memory (LLMWikis Analysis); AGENTS.md – Project Handoff Summary. 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-197 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Project Handoff System And Canonical AI Memory (Llmwikis Analysis)",
    "source_site":  "llmwikis.org",
    "source_url":  "https://llmwikis.org/",
    "canonical_url":  "https://aiwikis.org/llmwikis/files/raw-system-archives-llmwikis-agent-file-handoff-retired-source-archive-2-27b64d35/",
    "source_reference":  "raw/system-archives/llmwikis/agent-file-handoff/retired-source-archive-2026-06-13/2026-05-06/Improvement/canonical-ai-memory/Project Handoff System and Canonical AI Memory UAIX and LLMWikis.md",
    "file_type":  "md",
    "content_category":  "memory-file",
    "content_hash":  "sha256:27b64d353726803faa74fed14723cc9381b1d16055242c2b660ee358435e4847",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-05-06T15:19:06.9204821Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-197",
    "duplicate_role":  "primary",
    "related_files":  [

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