Skip to content

Adopt the AI Wiki as sibling pages beside topic index notes

  • Date: 2026-11-10
  • Status: Accepted
  • Tags: tooling workflow

Context

The community LifeOS skill (quanru/lifeos-skill) defines an AI Wiki: a {name}.AI.md page beside each topic note, synthesizing what the vault knows about that topic. Its rules assume Chinese PARA folders and a 7 索引/ index folder. Our vault uses English PARA folders and {name}.README.md index notes (ADR 0002, agent-context), so the rules had to be adapted (DEV-98, feature 7).

Decision

  • Pages are named {name}.README.AI.md beside the index note. This keeps the .README convention.
  • Frontmatter type: wiki is added to the allowed types in lifeos/agent-context.md.
  • The index and changelog live in 3. Resources/knowledge-management/AI Wiki/. That folder already holds PKM and Obsidian material.
  • Sections are in English: one-line summary, core judgments, material map, retrospective, next actions.
  • The /ai-wiki command (claude/commands/ai-wiki.md) maintains pages. It shows each draft and writes only after the user says yes.
  • Only topic index notes get a page. Source notes are never edited, and nothing is deleted.

Alternatives Considered

Option Why Rejected
Adopt the upstream rules unchanged (7 索引/, {name}.AI.md, Chinese headings) Doesn't match our folders or naming, and would need a second index folder.
Put the index in 3. Resources/AI/ That folder is for AI tools and learning, not the wiki itself.
Use the CLI for page generation The upstream CLI has no AI Wiki commands; pages are agent-written.

Consequences

Positive:

  • Pages sit next to the index notes they summarize, so they're found where the topic already is.
  • Decisions and next actions are recorded in one place per topic.

Negative / Trade-offs:

  • No deterministic checks: the lint step is agent-run and report-only.
  • Every update reads the topic's notes, so cost grows with topic size.
  • Sensitive topics must be summarized in general terms; the command enforces this.