An LLM Wiki should separate orientation, ownership, organization context, product context, architecture, operations, decisions, policies, agent rules, and onboarding. The structure below is intentionally boring: predictable paths are what make the wiki useful to agents.
Recommended folder structure
README.md
AGENTS.md
SCHEMA.md
WIKI_STRUCTURE_PLAN.md
WIKI_MIGRATION_PLAN.md
frontmatter.schema.json
page-registry.example.json
redirects.example.csv
aliases.example.yaml
INTAKE_OUTCOME_LEDGER.md
LINT_CHECKLIST.md
REVIEW_CHECKLIST.md
llms.example.txt
raw/
README.md
wiki/
index.md
log.md
knowledge-map.md
global/
index.md
coding-standards.md
organization.md
governance.md
source-map.md
{Site}/
index.md
source-policy.md
review-gates.md
concepts/
runbooks/
decisions/
_templates/
concept.md
guide.md
reference.md
source-record.md
evidence-log.md
redirect-record.md
Legacy expanded example tree:
llm-wiki/
README.md
INDEX.md
GOVERNANCE.md
TRUST_MODEL.md
CONTRIBUTING.md
CHANGELOG.md
organization/
MISSION.md
PRINCIPLES.md
TEAMS.md
GLOSSARY.md
products/
PRODUCT_OVERVIEW.md
ROADMAP.md
CUSTOMER_SEGMENTS.md
FEATURE_INVENTORY.md
architecture/
SYSTEM_OVERVIEW.md
SERVICES.md
DATA_FLOWS.md
DEPENDENCIES.md
ARCHITECTURE_DECISIONS.md
operations/
RUNBOOKS.md
INCIDENTS.md
RELEASE_PROCESS.md
SUPPORT_PROCESS.md
decisions/
DECISION_LOG.md
OPEN_QUESTIONS.md
TRADEOFFS.md
policies/
SECURITY.md
PRIVACY.md
DATA_HANDLING.md
AI_USAGE_POLICY.md
agent/
AGENT_INSTRUCTIONS.md
RETRIEVAL_GUIDE.md
ORCHESTRATION_RUNBOOK.md
TASK_PACKET_TEMPLATE.md
SUPPORT_ESCALATION_CHECKLIST.md
UPDATE_RULES.md
CITATION_RULES.md
SAFETY_BOUNDARIES.md
onboarding/
HUMAN_ONBOARDING.md
AGENT_ONBOARDING.md
QUICK_START.mdRoot index topology
Use the root INDEX.md differently depending on the system. A single codebase can use it as the all-files catalog and retrieval map. A multisite or multi-project LLM Wiki should keep the root index narrow: list the sub-wiki directories, link to each sub-wiki INDEX.md, and list only global files such as coding standards, organization policy, governance, source maps, and workspace.uai. Each sub-wiki owns its own all-files index.
Why these folders exist
| Folder | Job | Agent behavior |
|---|---|---|
organization/ |
Mission, principles, teams, glossary, and shared language. | Use for orientation and term disambiguation. |
products/ |
Product overview, roadmap, customer segments, and feature inventory. | Use to understand customer-facing context before implementation claims. |
architecture/ |
System overview, services, data flows, dependencies, and architecture decisions. | Use before suggesting technical changes. |
operations/ |
Runbooks, incidents, release process, and support process. | Summarize and check; do not execute protected actions. |
decisions/ |
Decision log, open questions, tradeoffs, and supersession notes. | Preserve uncertainty and rejected options. |
policies/ |
Security, privacy, data handling, and AI usage policy. | Treat as high-authority; require human review for edits. |
agent/ |
Agent instructions, retrieval, update, citation, and safety rules. | Read before editing; follow permission boundaries. |
onboarding/ |
Quick starts for people and agents. | Use for first-session context, not as full authority. |