Skip to content
aiWikis.org

Cross-Site Memory Atlas

--- title: "Cross-Site Memory Atlas" description: "AIWikis.org sits between two source systems and one implementation memory site." slug: "files/aiwikis/content-pages-027-cross-site-memory-atlas-md-253f8a07" status: "working-draft" trust_level: "generated-evidence" source_status: "current-source-file" content_type: "source-file" generated_by: "tools/sync-source-files.ps1" last_reprocessed: "2026-04-30" source_site: "aiwikis.org" source_url: "https://aiwikis.org/" canonical_url: "https://aiwikis.org/files/aiwikis/content-pages-027-cross-site-memory-atlas-md-253f8a07/" canonical: "https://aiwikis.org/files/aiwikis/content-pages-027-cross-site-memory-atlas-md-253f8a07/" source_reference: "content/pages/027-cross-site-memory-atlas.md" file_type: "md" content_category: "public-content" content_hash: "sha256:253f8a07f6c9b5b9b4fa0fc88168f4db20fba7c0a3ed1f615134a7247c703a57" last_fetched: "2026-04-30T22:07:25.2671233Z" last_changed: "2026-04-30T21:12:22.1713099Z" import_status: "unchanged" duplicate_group_id: "sfg-021" generated_explanation: true explanation_last_generated: "2026-04-30T22:07:25.2671233Z" source_domains:

tags:

related_files:

---

  • "aiwikis.org"
  • "ai-memory"
  • "provenance"
  • "aiwikis"
  • "retrieval"
  • "prompt-size-minimization"
  • ""

Cross-Site Memory Atlas

AIWikis.org sits between two 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-253f8a07/
Source referencecontent/pages/027-cross-site-memory-atlas.md
File typemd
Content categorypublic-content
Last fetched2026-04-30T22:07:25.2671233Z
Last changed2026-04-30T21:12:22.1713099Z
Content hashsha256:253f8a07f6c9b5b9b4fa0fc88168f4db20fba7c0a3ed1f615134a7247c703a57
Import statusunchanged
Raw source layerdata/sources/aiwikis/content-pages-027-cross-site-memory-atlas-md-253f8a07f6c9.md
Normalized source layerdata/normalized/aiwikis/content-pages-027-cross-site-memory-atlas-md-253f8a07f6c9.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

---
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, and AIWikis.org memory boundaries"
audience: "humans, ai-agents, maintainers"
---

# Cross-Site Memory Atlas

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

UAIX.org defines UAI-1 and AI Memory exchange. LLMWikis.org teaches deeper LLM Wiki practice. AIWikis.org preserves, demonstrates, and connects both without becoming either 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 |
| 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 |
| "What happened to a processed intake report?" | AIWikis.org | Record final memory, ledger outcome, and reviewed summaries |
| "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 |
| 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 AIWikis receives processed archive memory, AIWikis should:

1. Confirm source-site disposition.
2. Preserve raw memory under `raw/system-archives/`.
3. Write transfer evidence.
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 |
| "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.
- 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](./018-uaix-source-memory-guide.md) or [LLMWikis.org Source Memory Guide](./019-llmwikis-source-memory-guide.md).
3. Use `/uaix/`, `/llmwikis/`, `/files/`, `/concepts/`, and `/reports/` for focused evidence.
4. Use [Source Memory Operations Playbook](./028-source-memory-operations-playbook.md) when maintaining or extending the memory layer.
5. Use [Roadmap](./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-04-30T22:07:25.2671233Z
  • Source origin: current-source-workspace
  • Retrieval method: local-source-workspace
  • Duplicate group: sfg-021 (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-253f8a07/",
    "source_reference":  "content/pages/027-cross-site-memory-atlas.md",
    "file_type":  "md",
    "content_category":  "public-content",
    "content_hash":  "sha256:253f8a07f6c9b5b9b4fa0fc88168f4db20fba7c0a3ed1f615134a7247c703a57",
    "last_fetched":  "2026-04-30T22:07:25.2671233Z",
    "last_changed":  "2026-04-30T21:12:22.1713099Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-021",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-04-30T22:07:25.2671233Z"
}