Wiki Schema (LLM Maintainer Contract)

This file defines how the LLM maintains wiki/.

Shanepedia is not a generic notes vault. It is a founder/operator LLM wiki for Shane. The goal is to compile Shane's context into a durable markdown system that improves over time.

Core model

Shanepedia follows a three-layer model:

1. raw/sources/ is the immutable evidence layer.
2. wiki/ is the LLM-maintained synthesis layer.
3. AGENTS.md plus repo workflows are the maintainer contract.

This means the agent should not treat the repo as ordinary RAG over files. It should treat the wiki as compiled memory that must be updated, cross-linked, and kept coherent.

Page classes

• Overview pages: high-level synthesis (00_overview.md)
• Source summaries: one page per important source (sources/*.md)
• Entity pages: places/people/orgs (entities/*.md)
• Project pages: businesses, sites, products, trips, and research lanes (projects/*.md)
• Topic pages: cross-cutting themes (topics/*.md)
• Ops pages: planning and actions (ops/*.md)
• Maps: human and agent navigation entrypoints (maps/*.md)
• Dashboards: dynamic review pages intended for Obsidian plugins (dashboards/*.md)
• Travel pages: trip-specific planning artifacts (travel/*.md)

Link conventions

• Prefer wikilinks for durable internal navigation (elsalkb).
• Relative markdown links are acceptable when needed for rendering behavior.
• Every non-index page should link to at least one other wiki page.
• Prefer bidirectional links for key entities, topics, and projects.
• Important pages should be reachable from START_HERE.md, a map page, or a dashboard.

Ingest workflow

1. Read one raw source from raw/sources/.
2. Create or update a source summary page in wiki/sources/.
3. Update the most relevant entity, project, topic, ops, travel, map, or dashboard pages.
4. Record likely write-back targets when first-pass ingest is not enough yet.
5. If the source changes the big picture, update wiki/00_overview.md, wiki/START_HERE.md, or the relevant map page.
6. If the ingest creates a new durable insight, write it back as a first-class wiki page instead of leaving it in chat.
7. Run index and lint scripts.
8. Append operation in wiki/log.md.

Query workflow

1. Start with wiki/START_HERE.md and wiki/index.md unless the target page is already obvious.
2. Open the most relevant pages.
3. Synthesize an answer with explicit page citations when useful.
4. If the answer creates durable value, write it back as a new page, dashboard, canvas, or map update.
5. Prefer compounding the wiki over producing one-off chat output.

Metadata conventions

High-value pages should prefer frontmatter like:

title: Page Title
type: topic
status: active
area: strategy
last_updated: 2026-04-10
tags:
  - topic
related:
  - "[[../START_HERE.md]]"
suggested_related:
  - "[[../topics/example.md]]"

Preferred fields:

• title
• type
• status
• area
• last_updated
• tags
• related
• suggested_related for source pages or other notes that carry durable follow-up targets

Lint workflow

Run:

python3 scripts/wiki/update_index.py
python3 scripts/wiki/lint_wiki.py

Then fix:

• broken links
• orphan pages
• pages missing from index
• stale claims contradicted by newer source summaries
• missing navigation from maps, dashboards, or START_HERE.md

Shane-specific operating rule

Shanepedia should optimize for:

• Shane's actual preferences and working style
• low-friction browsing in Obsidian
• high-signal grounding for future agents
• durable founder context that outlives any single trip or project lane