Cross-Site Memory Operations
AIWikis is useful only if it remembers UAIX.org, LLMWikis.org, and Protocol5.com deeply without absorbing their authority.
Metadata
| Field | Value |
|---|---|
| Source site | aiwikis.org |
| Source URL | https://aiwikis.org/ |
| Canonical AIWikis URL | https://aiwikis.org/files/aiwikis/wiki-concepts-cross-site-memory-operations-md-f39531b5/ |
| Source reference | wiki/concepts/cross-site-memory-operations.md |
| File type | md |
| Content category | llm-wiki |
| Last fetched | 2026-05-02T01:47:31.8867765Z |
| Last changed | 2026-05-01T23:21:56.3772959Z |
| Content hash | sha256:f39531b5ed96ab606db0b965a8582820c2def50fd8b80c1954258c565a965c0f |
| Import status | unchanged |
| Raw source layer | data/sources/aiwikis/wiki-concepts-cross-site-memory-operations-md-f39531b5ed96.md |
| Normalized source layer | data/normalized/aiwikis/wiki-concepts-cross-site-memory-operations-md-f39531b5ed96.txt |
Current File Content
Structure Preview
- Cross-Site Memory Operations
- Root Problem
- Fix
- Operating Rule
- Non-Claims
- Related Nodes
Raw Version
---
uai_id: "96766fbc-e0cb-4439-90dc-970f820300fc"
type: "concept"
owner: "AIWikis maintainers"
status: "reviewed"
source_status: "local synthesis from reviewed cross-site public pages and handoff state"
sensitivity: "public-safe source-side memory"
agent_use: "load when work spans UAIX.org, LLMWikis.org, Protocol5.com, AIWikis.org, source authority, artifact ownership, source sync, archive consolidation, handoff export, or package evidence"
lineage:
- "content/pages/018-uaix-source-memory-guide.md"
- "content/pages/019-llmwikis-source-memory-guide.md"
- "content/pages/030-protocol5-source-memory-guide.md"
- "content/pages/027-cross-site-memory-atlas.md"
- "content/pages/028-source-memory-operations-playbook.md"
- "content/pages/031-source-site-outcome-routing.md"
- "wiki/concepts/source-site-report-preservation.md"
- ".uai/decisions.uai"
- ".uai/progress.uai"
source_trace:
- "docs/content-map.md"
- "docs/lessons-learned.md"
- "docs/recommendation-adjustments.md"
confidence: 0.86
confidence_label: "reviewed-local"
last_linted: "2026-05-01T22:45:00Z"
handoff_export: "include"
aliases:
- "Cross-Site Memory Operations"
- "Source Authority Routing"
- "AIWikis Source Memory Playbook"
---
# Cross-Site Memory Operations
AIWikis is useful only if it remembers UAIX.org, LLMWikis.org, and Protocol5.com deeply without absorbing their authority.
The working pattern is now explicit:
- UAIX.org remains canonical for UAI-1, AI Memory, Project Handoff, Agent File Handoff, validator/conformance, packages, governance, roadmap, and support boundaries.
- LLMWikis.org remains the handbook source for LLM Wiki structure, starter templates, trust labels, metadata, governance, source policy, and agent rules.
- Protocol5.com remains the parent Protocol5 brand and UAI .NET implementation package source; UAIX.org remains normative for UAI-1 standards claims.
- AIWikis.org preserves current source-file evidence, archive outcomes, dogfood lessons, public-safe guides, generated explanations, handoff exports, and package evidence.
## Root Problem
Generated source-file pages can show the current evidence, but they do not explain how to make authority decisions.
Without a cross-site atlas and operations playbook, future agents can make two mistakes:
- Treat an AIWikis archive or generated file page as fresher authority than the source site.
- Update public guidance without refreshing source sync, reports, `.uai` state, handoff export, or package evidence.
- Assume source-site staged work has changed AIWikis public memory without an explicit outcome-routing pass.
- Treat staged artifacts or summaries as proof that original processed reports were preserved in raw long-memory.
## Fix
AIWikis now has five public memory surfaces around the source systems:
- `content/pages/018-uaix-source-memory-guide.md` for UAIX-specific ownership, routes, update triggers, and non-claims.
- `content/pages/019-llmwikis-source-memory-guide.md` for LLMWikis-specific ownership, handbook routes, update triggers, and non-claims.
- `content/pages/030-protocol5-source-memory-guide.md` for Protocol5-specific parent-brand, UAI .NET package, route-contract, mirror, frozen-route, and UAIX-boundary memory.
- `content/pages/027-cross-site-memory-atlas.md` for authority routing, artifact ownership, memory layers, evidence flow, claim routing, and failure modes.
- `content/pages/028-source-memory-operations-playbook.md` for intake, source-change workflow, archive consolidation, generated evidence, handoff export, packaging, definition of done, and stop conditions.
- `content/pages/031-source-site-outcome-routing.md` for the intermediate state where source-site processing created staged work but did not automatically change AIWikis.
- `wiki/concepts/source-site-report-preservation.md` for the preservation check that confirms raw original reports have a copy/hash manifest before long-memory work is considered complete.
## Operating Rule
Every cross-site memory change should answer:
1. Which site owns the source claim?
2. Which AIWikis page explains it?
3. Which generated source-file page or report proves the current evidence?
4. Which `.uai` file preserves compact active truth?
5. Which checks or packages need to be refreshed?
6. Which claim is forbidden until the source site publishes support?
7. Was source-site staging expected to appear on AIWikis, and if so, where was the outcome recorded?
8. If original reports were expected to survive as long memory, which manifest records their source paths, destination paths, file counts, and checksums?
## Non-Claims
This operation model does not create hosted import validation, automatic repository writes, automatic LLM Wiki sync, SDK, CLI, certification, endorsement, package validation, deployment, or source-site authority.
## Related Nodes
- [[system-memory-archive]]
- [[deep-cognitive-archive]]
- [[uai-handoff-export-loop]]
- [[intake-outcome-ledger]]
- [[source-site-report-preservation]]
- [[protocol5-source-memory]]
- [[../index]]
Why This File Exists
This is a LLM Wiki memory 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 belongs to the source-side wiki layer. It preserves a focused concept, source proxy, graph record, or operating rule so the public site can cite reviewed conclusions without flattening every reason into a single long page.
Structure
The file is structured around these visible headings: Cross-Site Memory Operations; Root Problem; Fix; Operating Rule; Non-Claims; Related Nodes. 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-02T01:47:31.8867765Z - Source origin:
current-source-workspace - Retrieval method:
local-source-workspace - Duplicate group:
sfg-435(primary) - Historical hash records are stored in
data/hashes/source-file-history.jsonl.
Machine-Readable Metadata
{
"title": "Cross-Site Memory Operations",
"source_site": "aiwikis.org",
"source_url": "https://aiwikis.org/",
"canonical_url": "https://aiwikis.org/files/aiwikis/wiki-concepts-cross-site-memory-operations-md-f39531b5/",
"source_reference": "wiki/concepts/cross-site-memory-operations.md",
"file_type": "md",
"content_category": "llm-wiki",
"content_hash": "sha256:f39531b5ed96ab606db0b965a8582820c2def50fd8b80c1954258c565a965c0f",
"last_fetched": "2026-05-02T01:47:31.8867765Z",
"last_changed": "2026-05-01T23:21:56.3772959Z",
"import_status": "unchanged",
"duplicate_group_id": "sfg-435",
"duplicate_role": "primary",
"related_files": [
],
"generated_explanation": true,
"explanation_last_generated": "2026-05-02T01:47:31.8867765Z"
}