index.md and log.md let an agent route through a markdown graph without reading every file or depending on a heavy vector database. In one project, they are the scoped routing index and level-local chronological memory. In a multi-project wiki, the root pair is a workspace router: it names project-level index.md and log.md counterparts and leaves file-level detail inside each project.
index.md as a routing table
The index should be dense, boring, and scoped. A single-project index can list each page with path, type, one-sentence summary, tags, source status, and related pages. A multi-project root index should list only project namespaces, owners, status, project index.md, and project log.md links. The agent reads the root router, then opens the selected project index before opening deeper files.
| Index field | Why it belongs there | Example |
|---|---|---|
| Path | Lets the agent open the exact file without fuzzy search. | wiki/concepts/provenance.md |
| Type | Tells the agent whether to treat the page as source, concept, runbook, or synthesis. | concept |
| Summary | Lets routing happen before expensive page reads. | Defines claim lineage and audit paths. |
| Source status | Prevents weak pages from being used as strong evidence. | source-linked, source-needed, contradicted |
| Related pages | Creates deterministic next-hop routes. | [[trust-channel]], [[source-policy]] |
# Wiki Index
## Projects
| Namespace | Project index | Project log | Owner | Status |
|---|---|---|---|---|
| wiki/llmwikis/ | wiki/llmwikis/index.md | wiki/llmwikis/log.md | LLMWikis steward | reviewed |
| wiki/aiwikis/ | wiki/aiwikis/index.md | wiki/aiwikis/log.md | AIWikis steward | reviewed |
## Concepts
| Path | Summary | Tags | Source status |
|---|---|---|---|
| wiki/concepts/incremental-compilation.md | Explains ingest-time synthesis and why it compounds. | architecture, retrieval | reviewed |
| wiki/concepts/provenance.md | Defines source lineage for claims, outputs, and handoffs. | trust, audit | reviewed |
## Syntheses
| Path | Summary | Tags | Source status |
|---|---|---|---|
| wiki/syntheses/rag-vs-llm-wiki.md | Compares query-time retrieval with compiled markdown knowledge. | rag, architecture | draft |log.md as append-only memory
The log should never be rewritten to make history prettier. For one project, it is the audit trail for ingest, query, lint, manual review, and correction events. For a multi-project root, it records workspace-level coordination and links to project logs; it should not duplicate every project ingest or page change.
Use parseable prefixes so a human or script can filter recent work without a database. Good prefixes include ingest, query, lint, review, correction, blocked, and archive.
# Wiki Log
## 2026-04-27 coordination | project routing
- Added wiki/llmwikis/index.md and wiki/llmwikis/log.md to the root router.
- Added wiki/aiwikis/index.md and wiki/aiwikis/log.md to the root router.
- Detailed page updates stay in each project log.
## 2026-04-27 ingest | raw/papers/example-source.pdf
- Created wiki/sources/example-source.md.
- Updated wiki/concepts/incremental-compilation.md.
- Added contradiction: source date conflicts with older vendor note.
- Updated wiki/index.md.
## 2026-04-27 query | "How should we structure team review?"
- Read wiki/index.md and 4 selected pages.
- Created wiki/syntheses/team-review-loop.md after approval.
- No raw files changed.Routing algorithm
- Read index.md.
- Select candidate pages by path, title, summary, tags, and source status.
- Open only the smallest useful page set.
- Follow explicit wiki-links when the opened pages require more context.
- Read raw/ only when compiled pages are insufficient or a claim must be verified.
- Update the scoped index/log pair after any approved write. In a multi-project wiki, update the root pair only when project routing or workspace-level coordination changes.
When to add search
Start with index.md, filenames, frontmatter, and ordinary text search. Add BM25, Pagefind, vector search, or hybrid retrieval only when the wiki is large enough that deterministic routing is too slow or too brittle. Even then, search should point to compiled pages first.