Cross-Site Memory Atlas

AIWikis.org sits between four 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. ɩ.com / JustAnIota.com publishes compact AI messaging tools, source handoff state, logo/theme guidance, Concept Bridge, and HTML Keyless Extractor 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
ɩ.com / JustAnIota.com	Compact AI messaging implementation and public-site source	ɩ.com visible brand, JustAnIota.com canonical host, redirect-only short-domain role, Concept Bridge, HTML Keyless Extractor, logo/theme direction, handoff state, compact-message implementation notes	Document, preserve current source files, show processed-intake and short-domain release evidence, link to JustAnIota 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.

The root wiki index follows the same rule. wiki/index.md is a source-system router for the four sub-wikis and global-only records, not a flattened all-files catalog. Source-specific all-files maps belong in wiki/uaix/index.md, wiki/llmwikis/index.md, wiki/protocol5/index.md, and wiki/justaniota/index.md; cross-site and organization-level rules belong in wiki/global/index.md.

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-v2.7.0.zip?"	LLMWikis.org	Reference and observe the bundle, never relabel it
"Who publishes uai1-project-handoff-v2.7.0.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 is ɩ.com / JustAnIota.com?"	JustAnIota.com for public site and tooling; UAIX.org for UAI-1 authority	Say it is the JustAnIota compact-message tooling source and canonical host for the ɩ.com brand
"Does JustAnIota define UAI-1?"	UAIX.org	Say no: JustAnIota builds implementation profiles, tools, and examples on top of UAI boundaries
"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-v2.7.0.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-v2.7.0.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
JustAnIota public site, theme, and tools	JustAnIota.com	Preserve current source-file pages under /justaniota/ and explain the UAIX authority boundary
ɩ.com brand and redirect-only role	ɩ.com / JustAnIota.com	Preserve naming and host-boundary evidence; do not make AIWikis the domain authority
JustAnIota 2026-05-03 intake-processing manifest	AIWikis.org for long-memory copy; JustAnIota.com for source truth	Preserve raw originals, hashes, dispositions, and public-safe summaries under the JustAnIota source grouping
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 update that explains the outcome.
6. Update the relevant source guide, playbook, coverage, claim boundary, roadmap, lessons, recommendation state, and handoff files when durable memory changed.
7. 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 ɩ.com / JustAnIota.com changes, AIWikis should:

1. Read the JustAnIota source route or local JustAnIota workspace evidence.
2. Update the JustAnIota Source Memory Guide when the change affects brand/domain handling, compact-message tools, handoff state, logo/theme direction, public pages, or support boundaries.
3. Run transparent source-file sync so generated /justaniota/... pages and reports show current evidence.
4. Update public guidance and recommendation state only where AIWikis has preserved or applied the evidence.
5. Keep JustAnIota.com named as the source for JustAnIota implementation claims 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
"Where is the JustAnIota compact-message tooling evidence?"	ɩ.com / JustAnIota.com generated source pages, 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.
• Treating JustAnIota compact-message tools as UAI-1 standards authority.
• Leaving JustAnIota processed intake only under AIWikis raw memory instead of the /justaniota/ source grouping.
• 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. Use /uaix/, /llmwikis/, /protocol5/, /justaniota/, /files/, /concepts/, and /reports/ for focused evidence.
3. Use Source Memory Operations Playbook when maintaining or extending the memory layer.
4. Use Roadmap 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.