Wiki Page Format
Every wiki page should tell a future agent what is true now, why it is true, where it belongs, and what to update next.
Routing
Open Filing Decision Tree first when the question is where a page belongs. Open this page before creating or substantially rewriting the page body, especially for source-backed articles, entity pages, tool pages, protocols, and long references.
The wiki is compiled knowledge, not a transcript archive. Page format exists so agents can distinguish current synthesis from evidence history, route pages consistently, preserve provenance, and avoid graph drift. Source: AGENTS.md Page Format
Required Frontmatter
---
title: Page Title
type: skill | style | architecture | postmortem | design | tool | workflow | research | concept | person | project | place | philosophy | pattern | tension | era | transition | decision | career | interview-prep | meta | story | asset
created: YYYY-MM-DD
updated: YYYY-MM-DD
source: Source description
tags: [lowercase, hyphenated]
related: ["[[Other Page]]"]
---
Use the closest semantic type, not the physical directory at all costs. For operational namespaces such as resolver/, skill-resolver/, soul/, user/, heartbeat/, and agent-docs/, type: meta is usually correct unless the page is clearly a story, workflow, tool, or concept.
Optional but important:
aliases: required forpersonpages, useful for tools/projects/renamed pages.tier:1,2, or3for enrichment priority.longform: true: for coherent reference pages that are intentionally long.relationships: typed links when a page uses, extends, contradicts, or supersedes another page.generated: true: for generated source views or packs when the generator supports it. Generated pages must also follow Generated Surface Contract.routing_summary: compact trigger guidance when a page is loaded by agents or packs.
Body Structure
# Title> One-line summary that says what the page does- Current compiled truth organized by theme
- Decision tables, routing rules, examples, or failure modes when useful
---separator when required## Timeline- Append-only dated evidence entries
The separator is required for person, project, tool, and any page over 50 lines. Above the separator is rewritten when the current synthesis changes. Below it is append-only evidence.
Page Shape Variants
| Shape | Use for | Required behavior |
|---|---|---|
| Canonical synthesis article | Concepts, tools, projects, philosophies, design/style, architecture | Lead with the current model, not source chronology. |
| Entity page | Person, project, tool, institution | Include aliases/tier when relevant and keep timeline append-only. |
| Protocol or workflow | Meta/process pages | Include trigger, procedure, failure modes, verification, and closeout. |
| Directory hub/README | Category navigation | Explain what belongs, what does not, and first pages to read. |
| Resolver companion | wiki/resolver/ or wiki/skill-resolver/ extract |
Point back to the canonical resolver; do not fork the rule. |
| Generated source view | wiki/skills/<category>/ or generated pack |
Do not hand-edit generated bodies; update source and regenerate. |
| Ledger | Low-signal entities or compact inventories | Include aliases, promotion criteria, and source references. |
| Redirected/folded topic | Retired page identity | Preserve retrieval via aliases or wiki/meta/wiki-redirects.json. |
Compiled Truth
Compiled truth is the current best understanding. Rewrite it when better evidence arrives. Good compiled truth:
- starts with the key insight
- groups facts by theme
- links to related pages inline
- names contradictions when they matter
- removes stale wording instead of appending historical layers
- states ownership boundaries when adjacent pages are easy to confuse
Timeline
Timeline entries are evidence, not a second article. Format:
- **YYYY-MM-DD** | What happened and why it matters. [Source: source name, date]
Never silently delete a timeline entry. If a past entry was wrong, append a correction entry with the new evidence.
Computed Backlink Rendering
Do not author a ## Backlinks section. Backlinks are computed from wiki/_backlinks.json and rendered by the UI. Manual backlink sections create dead placeholders and pollute the graph. Use related: frontmatter and inline [[wikilinks]] for outgoing connections.
Length
Length follows the subject:
- under 15 lines: likely a stub; merge unless it has clear identity or redirect value
- 30-150 lines: normal compiled page
- over 400 lines: mark
longform: trueor split if it is really multiple topics
Do not split a coherent reference page just to satisfy a line count. Do split when one page has two durable subjects with different update paths.
Closeout
After substantive page edits, follow Index Logging Protocol:
npx tsx scripts/build-index.ts
qmd update && qmd embed
Run narrower doctors when the edit touches routing, generated packs, skills, config, or schema.
Timeline
- 2026-07-01 | Linked generated-page formatting to Generated Surface Contract so page shape and generated ownership use the same source/projection rule. Source: User request, 2026-07-01
- 2026-07-01 | Updated page format for the current wiki shape: resolver companions, generated skill pages, agent-doc packs, operational identity subtrees, page shape variants, and expanded frontmatter guidance. Source: User request, 2026-07-01
- 2026-06-18 | Expanded page format into an agent-ready schema with frontmatter, compiled-truth, timeline, backlink, and length rules. Source: User request, 2026-06-18; AGENTS.md
- 2026-05-31 | Meta page extracted from AGENTS.md page format contract. Source: AGENTS.md