Start Here

AIWikis.org is easiest to use when you choose the task first. It is not only a list of files. It is a routed memory system with public explanations, source-system hubs, generated evidence pages, reports, and source-side long memory.

If You Are New

1. Read What Is an LLM Wiki? for the basic idea.
2. Read How To Build an LLM Wiki for the sequence.
3. Read AIWikis Memory and Site Structure to understand the public pages, generated evidence pages, source-side wiki, and raw archive boundary.
4. Use Search when you know a word or source name.
5. Use Topics when you want concept navigation.

If You Need Source Authority

1. Start with Source Map to identify the source owner.
2. Use Memory Coverage Matrix to check whether AIWikis has enough local evidence.
3. Use Claim Boundary Register before writing public claims, package notes, roadmap language, or AI handoff summaries.

If You Are Maintaining AIWikis

1. Read Information Architecture and Search Guide before changing page names, URL hierarchy, route metadata, JSON-LD fields, search records, or SEO descriptions.
2. Read Source Memory Operations Playbook before changing source sync, archive consolidation, handoff export, generated evidence, or package-ready memory.
3. Read Source-Site Outcome Routing when source-site staged work is expected to become visible on AIWikis.
4. Read Intake Outcome Ledger when a dropped file has been digested and the human needs to know what happened.
5. Read Roadmap for current, next, later, and blocked work.

If You Are An AI Agent

1. Load the smallest page set that can answer the task.
2. Prefer Search, Topics, source-system hubs, and source guides before opening generated file evidence.
3. Use generated /uaix/uai-system/files/..., /llmwikis/uai-system/files/..., /protocol5/uai-system/files/..., /justaniota/uai-system/files/..., and /files/... pages only when you need provenance, source references, hashes, bounded previews, or source-file history.
4. Use Deep Cognitive Archive when the task needs reasoning history, rejected alternatives, contradictions, or lineage.
5. Use System Memory Archive for long-term memory only after source-site files have normal dispositions or explicit human approval.
6. Stop at human approval boundaries for policy, security, privacy, legal, production, architecture, or sensitive changes.

Fast Route Index

• Learn: What Is an LLM Wiki?, How To Build an LLM Wiki, Agent Rules, Governance.
• Find: Search, Topics, Source Provenance, Global File Index, Reports.
• Operate: Cross-Site Memory Atlas, Source Memory Operations Playbook, Source-Site Outcome Routing.
• Verify: Memory Coverage Matrix, Claim Boundary Register, Source Packages, Changelog.