Layered Publishing Architecture With LLM Wiki, UAI Memory, Project Handoff, And Claude Code

The strongest architecture for publishing durable, reviewable content to **llmwikis.org** is a **layered model** rather than a single-memory or single-agent model. In that model, **LLM Wiki** is the deep, long-lived k...

Metadata

Field	Value
Source site	llmwikis.org
Source URL	https://llmwikis.org/
Canonical AIWikis URL	https://aiwikis.org/llmwikis/files/raw-system-archives-llmwikis-source-site-report-preservation-2026-05-01-129dc4d2/
Source reference	raw/system-archives/llmwikis/source-site-report-preservation/2026-05-01/agent-file-handoff/Archive/2026-05-01/Improvement/llmwikis-integration-promoted/Layered Publishing Architecture with LLM and Claude Code.md
File type	md
Content category	memory-file
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-05-01T17:58:03.5739599Z
Content hash	sha256:129dc4d2ce3ae5cab5b0a2141498cee1c1dc0308e3df8bd871ab1277168863a5
Import status	unchanged
Raw source layer	data/sources/llmwikis/raw-system-archives-llmwikis-source-site-report-preservation-2026-05-01-agent-file-handoff-archi-129dc4d2ce3a.md
Normalized source layer	data/normalized/llmwikis/raw-system-archives-llmwikis-source-site-report-preservation-2026-05-01-agent-file-handoff-archi-129dc4d2ce3a.txt

Current File Content

Structure Preview

• Layered Publishing Architecture with LLM Wiki, UAI Memory, Project Handoff, and Claude Code
• Executive summary
• Goals and use cases
• Architecture and integration patterns
• Comparison table of alternatives and trade-offs
• Implementation blueprint
• Step-by-step flow
• Claude compatibility layer
• CLAUDE.md
• Claude Code
• Project-scoped MCP configuration
• Hooks-driven orchestration
• Local promotion and validation script
• Example: build a publication-evidence record only for reviewed public claims.
• Workflow sequence
• Data models and artifact schemas
• Sample .uai/context.uai
• LLMWikis Publication Program
• What This Is
• Goals
• Current Scope
• Out of Scope
• Sample llmwikis page frontmatter
• Entity relationship diagram

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: 37423
• Preview characters: 11924

# Layered Publishing Architecture with LLM Wiki, UAI Memory, Project Handoff, and Claude Code

## Executive summary

The strongest architecture for publishing durable, reviewable content to **llmwikis.org** is a **layered model** rather than a single-memory or single-agent model. In that model, **LLM Wiki** is the deep, long-lived knowledge system; **UAI AI Memory** is the compact, portable working packet; **UAI Project Handoff** is the transfer packet for ownership or execution changes; **Claude Code** is the execution and orchestration layer; and **UAI-1 plus the UAIX validator** provide auditable exchange and evidence when claims or artifacts must be portable beyond a single runtime. This is also the exact separation the official UAIX and LLMWikis materials advocate: LLM Wiki remains expansive and informative, while accepted operational truth is promoted into compact UAI artifacts and, where needed, UAI-1 evidence. citeturn14view1turn15view0turn18view0turn23view0

That layered approach is preferable to relying on Claude Code’s native memory alone. Claude Code’s persistent mechanisms are **CLAUDE.md** and **auto memory**; both are loaded as context, not enforced policy, and auto memory is **machine-local**, per repository, with only the first 200 lines or 25 KB of `MEMORY.md` loaded at session start. Anthropic explicitly notes that Claude Code reads `CLAUDE.md`, **not `AGENTS.md`**, although a `CLAUDE.md` file can import `AGENTS.md` so both systems share instructions. That makes Claude’s native memory useful for convenience and local continuity, but insufficient as the cross-team, cross-vendor, reviewable source of truth for publication work and developer handoff. citeturn21view2turn21view3

The main implementation implication is that the **officially documented UAIX public APIs are currently strongest for discovery, OpenAPI export, validation, and mock exchange**, not for writing or mutating AI Memory / Project Handoff state directly. The documented machine routes include `catalog`, `discovery`, `adoption-kit`, `openapi.json`, `validate`, `mock-exchange`, and related evidence routes. The public AI Memory and Project Handoff materials emphasize **file-based starter bundles**, manifests, `AGENTS.md`, `readme.human`, and `.uai` files; they also explicitly keep broader SDK / CLI / hosted-generator claims out of current support. Accordingly, the most rigorous design is to keep **write paths local and repository-based**, and use UAIX’s public routes for **validation and evidence**, while treating any higher-level memory or publication “API” described below as a **local adapter assumption** rather than an official UAIX write surface. citeturn11view1turn11view5turn12view1turn15view0

For **llmwikis.org**, the publication model should be **review-gated**, not autonomous live publishing. The public handbook defines strong metadata, trust labels, review dates, source-policy boundaries, agent rules, and security/privacy rules; it also states that AI-assisted drafts and notes are **not public truth by default**, and the current public handbook does **not** claim open editing, public MCP, certification, or automatic publication. In practical terms, the best publication workflow is: Claude drafts or updates wiki-page markdown, humans review, llmwikis metadata and citations are checked, then a maintainer merges or publishes. citeturn5view0turn16view1turn16view3turn28view2turn28view3turn28view0

The rest of this report therefore recommends a **governed, repository-first publication pipeline**: use LLM Wiki for research and institutional memory; promote reviewed facts into UAI AI Memory or Project Handoff; let Claude Code operate through `CLAUDE.md`, MCP, hooks, and optionally the Agent SDK or GitHub Actions; validate public exchange claims with UAI-1 routes; and publish only review-approved markdown that satisfies LLMWikis metadata, trust, and source-policy rules. citeturn15view0turn16view1turn16view2turn20view2turn7view3turn23view0

## Goals and use cases

The official materials describe a clean division of labor among the components in this stack. **LLM Wiki** is for durable organizational knowledge: policies, architecture, runbooks, decisions, glossary pages, and long source summaries. **UAI AI Memory** is a lightweight, file-based, reviewable packet for “current enough to act on” context. **Project Handoff** is the specific transfer pattern that coordinates `AGENTS.md`, `readme.human`, and typed `.uai` files. Claude Code is the agentic coding layer that can read code, edit files, run commands, connect to tools through MCP, and automate lifecycle events through hooks. citeturn18view0turn4view0turn12view1turn5view6turn7view2turn7view1

The resulting use cases map naturally to the user’s requested publication scenario.

| Goal or use case | Primary artifact | Why this layer is the best fit | Source basis |
|---|---|---|---|
| Knowledge base augmentation | LLM Wiki pages, source summaries, index/log updates | LLMWikis positions the wiki as the durable, human-readable, machine-consumable knowledge system with explicit ownership, trust labels, metadata, and governance. | citeturn18view0turn17view0turn18view2turn28view2 |
| Collaborative editing | llmwikis markdown plus review workflow | LLMWikis requires metadata, owner roles, review cycles, and human review for sensitive or authoritative changes. | citeturn16view2turn16view3turn18view3turn28view2turn28view3 |
| Project continuity across sessions | UAI AI Memory plus Claude `CLAUDE.md` | UAIX says AI Memory is the compact operating memory future actors should load; Anthropic says Claude Code’s native memory is local context, not durable cross-team truth. | citeturn4view0turn14view1turn21view2turn21view3 |
| Developer or vendor handoff | UAI Project Handoff | Project Handoff packages current state, constraints, owners, checks, and transfer context through `AGENTS.md`, `readme.human`, and `.uai` files. | citeturn12view1turn13view0turn13view2turn13view5 |
| Public support or interoperability claims | UAI-1 messages plus validator output | UAIX positions UAI-1 as the portable public exchange and evidence layer; validator-backed support evidence is part of the release path. | citeturn23view0turn11view2turn25view3 |
| Automated drafting, editing, and packaging | Claude Code CLI / Agent SDK / GitHub Actions | Claude Code supports tool use, MCP, hooks, project memory, session resume, and GitHub Actions built on the Agent SDK. | citeturn7view1turn7view2turn20view0turn20view2turn7view3 |

The most important design principle is **promotion discipline**. UAIX says LLM Wiki memory stays background until reviewed and promoted into named UAI package files, docs, code, release notes, roadmap state, or machine artifacts. LLMWikis says AI-assisted drafts and notes are not public truth by default, and that sources, trust labels, freshness, and owner/reviewer signals must stay visible. Together, those rules create a publication model that is strong for both AI productivity and editorial rigor. citeturn15view0turn16view1turn28view3

## Architecture and integration patterns

A practical architecture for this stack has five layers: **sources**, **deep wiki**, **portable memory / handoff**, **agent orchestration**, and **publication / evidence**. LLMWikis’ architecture guidance explicitly separates raw sources from synthesized wiki pages, and makes navigation and lifecycle state explicit. UAIX adds the portable packet layer for accepted operational truth and exchange evidence. Anthropic adds the execution layer through Claude Code, MCP, hooks, the Agent SDK, and GitHub Actions. citeturn18view1turn15view0turn23view0turn20view2turn7view3

```mermaid
flowchart LR
    A[Raw sources and research inputs] --> B[LLM Wiki deep memory]
    B --> C[Reviewed promotion step]
    C --> D[UAI AI Memory bundle]
    C --> E[UAI Project Handoff packet]
    D --> F[Claude Code or Agent SDK]
    E --> F
    F --> G[Local build and publication adapter]
    G --> H[llmwikis.org content PR or CMS draft]
    F --> I[UAI-1 record]
    I --> J[UAIX validator and conformance evidence]

    subgraph Governance
      K[Metadata, trust labels, review dates]
      L[Human approval gates]
    end

    B --- K
    D --- L
    E --- L
    H --- L
    J --- L
```

The cleanest Claude integration point is to treat **`AGENTS.md` as the canonical handoff front door** for multi-agent portability, and then let **`CLAUDE.md` import it** for Claude Code compatibility. Anthropic documents that Claude Code reads `CLAUDE.md`, not `AGENTS.md`, but supports `@AGENTS.md` imports. That means a repo can keep UAI Project Handoff conventions without maintaining parallel, drifting instruction files. citeturn21view3

The best tool-connection pattern is typically **project-scoped MCP** plus **hooks**. Anthropic documents project-scoped MCP servers in `.mcp.json`, designed for version control and team sharing, with approval prompts before use. Anthropic also documents hooks as shell commands, HTTP endpoints, or LLM prompts that receive JSON on lifecycle events; `PreToolUse` can allow, deny, ask, or defer tool calls and even modify inputs, while `PostToolUse` and `Stop` are good places to trigger memory updates, lint, or publication-stage packaging. citeturn20view3turn19view0turn19view1

The **public UAIX API pattern** is a read/validate/evidence pattern. UAIX documents `catalog`, `discovery`, `adoption-kit`, `openapi.json`, `validate`, and `mock-exchange` routes, and provides code examples in curl, PowerShell, Python, and TypeScript for consuming them. UAI-1 complements MCP and OpenAPI rather than replacing them: MCP handles runtime tool integration; UAI-1 handles the portable public record and validator-backed evidence. citeturn11view1turn25view3turn23view0

The **publication pattern for llmwikis.org** should be a docs-as-code path with explicit metadata, review, and source policy. LLMWikis’ implementation checklist calls for a repository or wiki platform with exportable files and history, metadata on each page, named owners, trust labels, sensitivity labels, agent instructions, linting, and human review for AI-generated edits before connecting retrieval systems. That is a strong match for a content PR workflow or a CMS-draft workflow fed by repository files. citeturn16view2turn18view4turn28view2

### Comparison table of alternatives and trade-offs

The table below is a synthesis of the documented capabilities and limits of UAIX, LLMWikis, and Anthropic’s Claude tooling.

| Option | Strengths | Weaknesses | Best fit | Evidence basis |
|---|---|---|---|---|
| **Layered stack: LLM Wiki + UAI Memory + Project Handoff + Claude Code** | Best separation between deep knowledge, portable action context, and agent execution; strongest auditability and publication discipline | More moving parts and more governance work | Recommended default for llmwikis.org publication and cross-team handoff | citeturn15view0turn16view0turn20view2turn23view0 |
| **Claude Code only: `CLAUDE.md` + auto memory** | Fastest to start; excellent local productivity | Auto memory is machine-local and limited at startup; not a portable team handoff format | Solo or short-lived projects | citeturn21view2turn21view3 |
| **LLM Wiki + Claude Code, no UAI bundles** | Strong deep knowledge base and governed docs | Weaker “current working packet” and weaker structured transfer boundary | Internal documentation-heavy teams with low handoff complexity | citeturn18view0turn16view0turn15view0 |
| **UAI Memory / Project Handoff + docs-as-code, no full LLM Wiki** | Strong portable continuity and transfer packet | Poorer institutional memory and source-synthesis depth | Smaller engineering orgs or bounded delivery pipelines | citeturn4view0turn12view1turn14view1 |

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: Layered Publishing Architecture with LLM Wiki, UAI Memory, Project Handoff, and Claude Code; Executive summary; Goals and use cases; Architecture and integration patterns; Comparison table of alternatives and trade-offs; Implementation blueprint; Step-by-step flow; Claude compatibility layer. 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-090 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Layered Publishing Architecture With LLM Wiki, UAI Memory, Project Handoff, And Claude Code",
    "source_site":  "llmwikis.org",
    "source_url":  "https://llmwikis.org/",
    "canonical_url":  "https://aiwikis.org/llmwikis/files/raw-system-archives-llmwikis-source-site-report-preservation-2026-05-01-129dc4d2/",
    "source_reference":  "raw/system-archives/llmwikis/source-site-report-preservation/2026-05-01/agent-file-handoff/Archive/2026-05-01/Improvement/llmwikis-integration-promoted/Layered Publishing Architecture with LLM and Claude Code.md",
    "file_type":  "md",
    "content_category":  "memory-file",
    "content_hash":  "sha256:129dc4d2ce3ae5cab5b0a2141498cee1c1dc0308e3df8bd871ab1277168863a5",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-05-01T17:58:03.5739599Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-090",
    "duplicate_role":  "primary",
    "related_files":  [

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