LLM Wiki Structure

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

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
    UPDATE_RULES.md
    CITATION_RULES.md
    SAFETY_BOUNDARIES.md
  onboarding/
    HUMAN_ONBOARDING.md
    AGENT_ONBOARDING.md
    QUICK_START.md

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.