LLM Wiki

Appearance

Built 26/04/17 09:08commit f8ff6f9

Vault Architecture ​

中文 | English

Summary ​

The vault is organized as a three-layer system: source material in raw/ whose substance stays stable even if paths are reorganized, durable synthesized knowledge in wiki/, and an AGENTS.md schema that defines how the model updates the wiki over time.

Layers ​

  • raw/ is the source-of-truth collection. Files are curated by the human; only path-maintenance edits needed for raw refactors are allowed. This layer may include markdown, screenshots, and local image assets.
  • wiki/ is the maintained knowledge layer. It holds source notes, concepts, entities, topics, and durable answers.
  • AGENTS.md is the maintenance contract. It defines workflows, page roles, and update conventions.

Operational Primitives ​

  • index.md and index.zh.md are the content maps. They should be read first to decide which pages matter for a task.
  • log.md is the time-ordered activity record for ingests, durable queries, and lint passes.
  • Source pages in wiki/sources/ document what each raw file contributes and which long-lived pages changed because of it.
  • Top-level entry files should stay compact and link outward; if index.md turns into a dump, maintenance gets slower and the routing layer stops doing its job.

Design Choices ​

  • The architecture favors persistent synthesis over query-time rediscovery.
  • The wiki should evolve by revising canonical pages, not by accreting loosely related duplicates.
  • Reusable operational bundles such as the llm-wiki skill can add root resolution, automation, and safe-maintenance helpers without replacing markdown as the primary knowledge system.
  • Optional tooling such as search, Dataview, or slide generation is secondary to the markdown corpus itself.
  • The human stays responsible for curation and direction; the model owns the maintenance burden.
  • AGENTS.md should act as a routing layer into the rest of the vault, not as a monolithic rule dump.
  • Progressive disclosure matters: small stable entry points age better than one giant instruction surface.

Open Questions ​

  • When the wiki grows beyond index-first navigation, what is the minimum useful local search layer?
  • Which domains deserve dedicated entities/ pages versus being absorbed into topics/?

Sources ​