Skip to content
aiWikis.org

Cross-Site Memory Atlas

AIWikis.org sits between three source systems and one implementation memory site.

Metadata

FieldValue
Source siteaiwikis.org
Source URLhttps://aiwikis.org/
Canonical AIWikis URLhttps://aiwikis.org/files/aiwikis/content-pages-027-cross-site-memory-atlas-md-19bf01e9/
Source referencecontent/pages/027-cross-site-memory-atlas.md
File typemd
Content categorypublic-content
Last fetched2026-05-03T02:48:13.1276041Z
Last changed2026-05-03T02:38:27.3999121Z
Content hashsha256:19bf01e9d600bbe563a20e111596427d84bf58a5ed6c6722e42fefbb376e9391
Import statuschanged
Raw source layerdata/sources/aiwikis/content-pages-027-cross-site-memory-atlas-md-19bf01e9d600.md
Normalized source layerdata/normalized/aiwikis/content-pages-027-cross-site-memory-atlas-md-19bf01e9d600.txt

Current File Content

Structure Preview

  • Cross-Site Memory Atlas
  • System Roles
  • Authority Matrix
  • Artifact Ownership
  • Memory Layers
  • Evidence Flow
  • Claim Routing
  • Common Failure Modes
  • Reader Path

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.

---
title: "Cross-Site Memory Atlas"
slug: "cross-site-memory-atlas"
status: "working-draft"
trust_level: "reviewed"
source_status: "AIWikis operating atlas for UAIX.org, LLMWikis.org, Protocol5.com, and AIWikis.org memory boundaries"
audience: "humans, ai-agents, maintainers"
---

# Cross-Site Memory Atlas

AIWikis.org sits between three source systems and one implementation memory site.

UAIX.org defines UAI-1 and AI Memory exchange. LLMWikis.org teaches deeper LLM Wiki practice. Protocol5.com publishes Protocol5 parent-brand, Mathematics, and UAI .NET implementation package evidence. AIWikis.org preserves, demonstrates, and connects them without becoming any source authority.

This atlas is the map a human or AI agent should read before making cross-site claims.

## System Roles

| Site | Primary Role | What It Owns | What AIWikis May Do |
| --- | --- | --- | --- |
| UAIX.org | Standards and evidence authority | UAI-1, AI Memory, Project Handoff, Agent File Handoff, validator/conformance, roadmap, governance, UAIX packages | Document, preserve current source files, explain dogfood use, link to canonical routes |
| LLMWikis.org | Handbook and pattern authority | LLM Wiki structure, starter template, trust model, metadata, source policy, governance, agent rules, LLM Wiki package guidance | Document, preserve current source files, demonstrate implementation, link to handbook routes |
| Protocol5.com | Parent brand and UAI .NET implementation package source | Protocol5 Mathematics, UAI .NET Hub, NuGet artifacts, starter ZIPs, route contracts, package mirrors, compatibility endpoints | Document, preserve current source files, show package evidence, link to Protocol5 for implementation and UAIX for UAI authority |
| AIWikis.org | Long-term memory and dogfood site | Local source archive, generated file pages, public-safe guides, lessons, recommendations, package evidence, local Project Handoff export | Preserve evidence, expose retrieval paths, record outcomes, build practical examples |

The first rule is simple: source authority does not move just because AIWikis stores a richer memory copy.

## Authority Matrix

| Claim Type | Source Of Truth | AIWikis Use |
| --- | --- | --- |
| "What is UAI-1?" | UAIX.org | Summarize and route readers to UAIX |
| "What is AI Memory?" | UAIX.org | Show package and wizard evidence from UAIX |
| "How should Project Handoff work?" | UAIX.org | Dogfood the pattern and record friction |
| "How should Agent File Handoff work?" | UAIX.org | Use local intake buckets and outcome ledgers as evidence |
| "What is an LLM Wiki?" | LLMWikis.org | Explain the pattern and show AIWikis implementation |
| "How should raw/wiki/config be structured?" | LLMWikis.org | Demonstrate a local source-side version |
| "Who publishes `llm-wiki-starter-bundle.zip`?" | LLMWikis.org | Reference and observe the bundle, never relabel it |
| "Who publishes `uai1-project-handoff.zip`?" | UAIX.org | Mirror only as UAIX-owned dogfood install evidence |
| "Who publishes Protocol5 UAI .NET packages?" | Protocol5.com | Observe package evidence and route back to Protocol5 implementation pages |
| "Is Protocol5.com the UAI-1 standards authority?" | UAIX.org for standards; Protocol5.com for implementation packages | Say no: Protocol5 distributes implementation assets and links back to UAIX |
| "What happened to a processed intake report?" | AIWikis.org | Record final memory, ledger outcome, and reviewed summaries |
| "Why did source-site processing not change AIWikis.org?" | Source repository for staging; AIWikis.org for outcome routing | Say that staged source-site work needs an explicit AIWikis routing pass before public AIWikis guidance changes |
| "Is a feature currently supported?" | Source site roadmap plus AIWikis roadmap for local state | Keep current, next, later, and blocked claims separate |

## Artifact Ownership

| Artifact | Owner | AIWikis Handling |
| --- | --- | --- |
| UAI-1 schemas, registry, validator behavior | UAIX.org | Preserve source-file pages and link to UAIX |
| UAIX AI Memory Package Wizard outputs | UAIX.org | Document generated system profile, receiver brief, startup packet, overlay JSON, and optional LLM Wiki plan |
| `uai1-project-handoff.zip` | UAIX.org | May mirror for wp-admin dogfood only with UAIX labels |
| LLMWikis starter template and handbook pages | LLMWikis.org | Preserve generated file pages and public guide summaries |
| `llm-wiki-starter-bundle.zip` | LLMWikis.org | Reference as upstream; do not ship as AIWikis product |
| Protocol5 UAI .NET packages | Protocol5.com | Observe and preserve package metadata; do not relabel as AIWikis or standards authority |
| Protocol5 route contract and package mirrors | Protocol5.com | Preserve current file pages and explain the UAIX authority boundary |
| Protocol5 Prime/Fibonacci generated route trees | Protocol5.com | Do not sync generated numeric pages into AIWikis unless a human explicitly requests compatibility analysis |
| AIWikis reviewed public pages | AIWikis.org | Render from `content/pages/` and package into `aiwikis-core/data/pages` |
| AIWikis raw system archives | AIWikis.org | Store already-dispositioned cross-site memory; do not expose raw files as public truth |
| AIWikis source-side wiki nodes | AIWikis.org | Keep deep memory, decisions, contradictions, and export-eligible knowledge |
| AIWikis Project Handoff export | AIWikis.org | Treat as local dogfood evidence, not UAIX certification |

## Memory Layers

AIWikis keeps several layers because one layer cannot do every job.

| Layer | Job | Public? |
| --- | --- | --- |
| Reviewed public pages | Polished guidance, routes, and explanations | Yes |
| Generated source-file pages | Focused current-file views with metadata and explanations | Yes, redacted for local paths |
| `.uai` handoff files | Compact active context for future AI agents | Source-side and release evidence |
| `raw/system-archives/` | Long-term memory for already-dispositioned reports | Source-side only unless summarized |
| `wiki/` nodes | Deep reasoning, provenance, lessons, and selected export memory | Source-side, selectively exported |
| `reports/` | Sync, recovery, duplicate, broken-link, and final-content audit output | Public-safe reports plus local evidence |
| `dist/handoff/` | Generated local Project Handoff packet | Release/dogfood evidence |

The practical result is prompt-size control: agents can load one page, one file record, or one node instead of dragging an entire site into context.

## Evidence Flow

When UAIX.org changes, AIWikis should:

1. Read the UAIX source route or local UAIX workspace evidence.
2. Update the UAIX Source Memory Guide when the change affects claims, routes, packages, wizard behavior, or support boundaries.
3. Run transparent source-file sync so generated `/uaix/...` pages and reports show the current file evidence.
4. Update roadmap, lessons, recommendations, `.uai` state, and package evidence when the change affects AIWikis behavior.
5. Keep UAIX.org named as authority.

When LLMWikis.org changes, AIWikis should:

1. Read the LLMWikis source route or local LLMWikis workspace evidence.
2. Update the LLMWikis Source Memory Guide when the change affects handbook claims, starter bundles, governance, metadata, source policy, or agent rules.
3. Run transparent source-file sync so generated `/llmwikis/...` pages and reports show current evidence.
4. Update public guidance and recommendation state only where AIWikis has applied the pattern.
5. Keep LLMWikis.org named as handbook authority.

When a source-site processing job creates staged outcomes but the human expects AIWikis visibility, AIWikis should:

1. Confirm what the source site actually changed.
2. Preserve the distinction between original reports, staged drafts, reviewed source-site edits, and public truth.
3. Confirm whether original processed reports have a raw AIWikis manifest with file counts and checksums when long-memory preservation is expected.
4. Confirm whether newer current-source files changed after older report preservation. If implementation, test, discovery, starter, route, or support-boundary files changed, create a current-source digest before calling AIWikis memory complete.
5. Add an Intake Outcome Ledger entry or Source-Site Outcome Routing (source-relative: ./031-source-site-outcome-routing.md) update that explains the outcome.
5. Update the relevant source guide, playbook, coverage, claim boundary, roadmap, lessons, recommendation state, and handoff files when durable memory changed.
6. Keep unsupported automation, API, MCP, certification, endorsement, and deployment claims staged or blocked until source evidence exists.

When Protocol5.com changes, AIWikis should:

1. Read the Protocol5 source route or local Protocol5 workspace evidence.
2. Update the Protocol5 Source Memory Guide when the change affects parent-brand structure, UAI .NET packages, route contracts, package mirrors, compatibility endpoints, or source-authority boundaries.
3. Run transparent source-file sync so generated `/protocol5/...` pages and reports show current evidence.
4. Update public guidance and recommendation state only where AIWikis has preserved or applied the evidence.
5. Keep Protocol5.com named as implementation package source and UAIX.org named as UAI-1 authority.

When AIWikis receives processed archive memory, AIWikis should:

1. Confirm source-site disposition.
2. Preserve raw memory under `raw/system-archives/`.
3. Write transfer evidence with source paths, destination paths, file counts, and checksums.
4. Compile public-safe summary pages or wiki nodes.
5. Record the outcome in the Intake Outcome Ledger.

## Claim Routing

| If The User Asks | Answer From |
| --- | --- |
| "What should my AI Memory package contain?" | UAIX AI Memory route and wizard evidence, with AIWikis dogfood notes |
| "Should I use an LLM Wiki?" | LLMWikis handbook plus UAIX optional LLM Wiki package guidance |
| "Where do I get Protocol5 UAI .NET packages?" | Protocol5.com package routes, with UAIX.org for standards authority |
| "Can AIWikis validate my package?" | No, unless a future source-supported validator exists |
| "Where did this file come from?" | AIWikis generated source-file page and reports |
| "Why did this recommendation change?" | AIWikis lessons, recommendation adjustments, decisions, and source-side wiki nodes |
| "Is this production live?" | AIWikis Roadmap and deployment boundary |
| "Who owns this package?" | Source Packages page plus this atlas |

## Common Failure Modes

- Treating AIWikis archive copies as current UAIX or LLMWikis truth.
- Treating source-site staged drafts as AIWikis public changes without an explicit outcome-routing pass.
- Treating old source-site report preservation as proof that newer current-source work was retained.
- Treating Protocol5 implementation mirrors as UAIX standards authority.
- Copying source-site package names into AIWikis product language.
- Hiding a source-site roadmap boundary inside AIWikis enthusiasm.
- Letting generated source-file pages replace human-scale guides.
- Letting public pages become too broad to retrieve efficiently.
- Letting `.uai` files bloat into deep archives.
- Running package builds without checking support-boundary copy.

## Reader Path

1. Read this atlas for the cross-site shape.
2. Read the UAIX.org Source Memory Guide (source-relative: ./018-uaix-source-memory-guide.md), LLMWikis.org Source Memory Guide (source-relative: ./019-llmwikis-source-memory-guide.md), or Protocol5.com Source Memory Guide (source-relative: ./030-protocol5-source-memory-guide.md).
3. Use `/uaix/`, `/llmwikis/`, `/protocol5/`, `/files/`, `/concepts/`, and `/reports/` for focused evidence.
4. Use Source Memory Operations Playbook (source-relative: ./028-source-memory-operations-playbook.md) when maintaining or extending the memory layer.
5. Use Roadmap (source-relative: ./017-roadmap.md) before turning local package truth into a live-site claim.

The atlas should make the memory system boringly clear: each source keeps authority, AIWikis keeps memory, and every claim has a route home.

Why This File Exists

This is a public content source 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 file is a focused source unit. Its path, headings, and metadata give an agent a retrieval handle that is smaller than loading the entire site or repository.

Structure

The file is structured around these visible headings: Cross-Site Memory Atlas; System Roles; Authority Matrix; Artifact Ownership; Memory Layers; Evidence Flow; Claim Routing; Common Failure Modes. 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-047 (primary)
  • Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Cross-Site Memory Atlas",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/files/aiwikis/content-pages-027-cross-site-memory-atlas-md-19bf01e9/",
    "source_reference":  "content/pages/027-cross-site-memory-atlas.md",
    "file_type":  "md",
    "content_category":  "public-content",
    "content_hash":  "sha256:19bf01e9d600bbe563a20e111596427d84bf58a5ed6c6722e42fefbb376e9391",
    "last_fetched":  "2026-05-03T02:48:13.1276041Z",
    "last_changed":  "2026-05-03T02:38:27.3999121Z",
    "import_status":  "changed",
    "duplicate_group_id":  "sfg-047",
    "duplicate_role":  "primary",
    "related_files":  [

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