An LLM Wiki is a durable internal knowledge base. AI Memory is a portable file-based context bundle for a task, project, handoff, onboarding flow, audit, or agent run. Mature organizations often use both: the wiki keeps cold depth, and AI Memory keeps hot working truth.
| Use case | LLM Wiki | AI Memory |
|---|---|---|
| Durability | Long-lived source of truth for an organization or domain. | Portable working context for a bounded job. |
| Ownership | Maintained by page owners, reviewers, and governance rules. | Prepared by a project owner or tool for a recipient or agent run. |
| Scope | Broad institutional knowledge and operating memory. | Selected context needed right now. |
| Context budget | Cold memory for research, old history, source summaries, and recovery evidence. | Hot memory for current constraints, accepted decisions, next work, and checks. |
| Project Handoff | The wiki may provide the durable source material. | Project Handoff is a specific AI Memory transfer packet. |
| Relationship | Can generate or link to AI Memory bundles. | Should link back to durable wiki pages when possible. |
Recommended Positioning
- Use LLM Wiki when the organization needs a shared, durable, searchable source of truth.
- Use AI Memory when a project, agent, contractor, team, or stakeholder needs a portable context packet.
- Use both when durable knowledge needs to become working context for a specific task, handoff, onboarding flow, audit, or agent run.
- Use
workspace.uaiwhen one editor workspace contains multiple sites or codebases, so the target site is resolved before any site-local.uaimemory loads. - Before a handoff bundle gets large, copy old detail into cold memory with a manifest and keep the active packet focused on current truth.
UAIX memory-plan alignment
When a project uses both a compact UAIX AI Memory package and a deeper LLM Wiki, keep the boundary explicit. The optional LLM_WIKI_MEMORY_PLAN.md tells the receiver where durable wiki memory lives, how it is promoted, and why background memory does not override current project truth.
| Generated file | What it should capture | LLM Wiki mapping |
|---|---|---|
UAI_MEMORY_SYSTEM_PROFILE.md |
Collaboration model, source authority, testing, deployment, review, evidence, conflict, risk, and rollback policies. | Map these fields to wiki governance, source policy, review gates, and release evidence. |
UAI_MEMORY_RECEIVER_BRIEF.md |
First-read instructions, what not to assume, support boundaries, and targeted-check expectations. | Point to the smallest useful wiki pages and the current hot-context files. |
UAI_MEMORY_STARTUP_PACKET.md |
One bounded startup surface for the next human, team, or AI before broad work starts. | Keep it hot and compact; link back to durable wiki pages instead of copying the whole wiki. |
LLM_WIKI_MEMORY_PLAN.md |
Wiki root, index, log/evidence paths, steward, source boundary, promotion rules, and update timing. | Treat wiki memory as background until reviewed and promoted into accepted project truth. |
UAIX AI Memory
Canonical UAIX page for AI Memory framing and supported starter bundles.
UAIX AI Memory Package Wizard
Canonical UAIX wizard for generated local package files, optional LLM Wiki memory-plan output, and supported starter ZIP links.
UAIX Project Handoff
Canonical transfer packet guidance for moving ownership.
LLM Wiki Starter Bundle
Durable internal wiki skeleton that can later feed portable context bundles.