Templates keep the wiki from drifting into unstructured essays. They also make pages easier for humans, search crawlers, and future agents to evaluate because every page exposes purpose, status, evidence, limitations, and next links in a predictable shape.
Required page metadata
---
title: "Page title"
type: concept | source-summary | how-to | runbook | comparison | model | benchmark | protocol | tool
status: draft | reviewed | needs-update | contradicted | archived
source_status: source-linked | source-needed | canonical-linked | derived
last_reviewed: YYYY-MM-DD
canonical_source:
related:
- /architecture/three-layer-architecture/
---Template families
Architecture Guide
Problem, system boundary, folder or service shape, tradeoffs, failure modes, evidence boundary, and next implementation step.
How-To Tutorial
Prerequisites, exact procedure, copyable prompt or command, expected output, done-means checklist, and rollback or failure guidance.
Operations Runbook
Trigger, inputs, steps, severity, stop condition, rollback path, checks, log entry, and escalation rule.
Schema Page
Rule purpose, required fields, allowed values, examples, lint checks, source trace rules, and context-pollution warning.
Example Build
Audience, folder tree, operating rhythm, prompts, roles, source boundaries, policies, and scale-up notes.
Navigation Mechanic
Routing file shape, update rule, query algorithm, graph links, failure mode, and search-upgrade threshold.
Concept
Definition, why it matters, mechanics, limitations, examples, common confusions, source notes, and related pages.
Protocol
Summary, authority boundary, when to use, when not to use, core fields, examples, validator behavior, comparisons, and canonical links.
Comparison
Summary judgment, quick table, decision tree, detailed criteria, use-together pattern, caveats, and source links.
Model Profile
Identity, modalities, capability profile, evidence trail, benchmark caveats, architecture, deployment, interop readiness, and limits.
Benchmark
What it measures, why it matters, official source, scoring method, limitations, contamination risk, update cadence, and related models.
Implementation Tool
What it does, supported inputs, workflows, common errors, code examples, exportability, reviewability, and related standards.
Universal article skeleton
# Title
Status panel: type, authority, review date, source status.
Lead: define the topic and who should care.
## What it is
Plain definition with source boundary.
## Why it matters
Practical consequence for builders or reviewers.
## How it works
Mechanics, workflow, fields, or architecture.
## Evidence and caveats
Sources, dates, limitations, contradictions, stale areas.
## Example
Small concrete example, prompt, folder tree, table, or decision rule.
## Related pages
Internal links that keep the graph navigable.Publish gates
- The lead answers what the topic is, who uses it, and what problem it solves.
- The page has source status before it has confident prose.
- Time-sensitive claims show source date or visible review cadence.
- The page links to at least two relevant internal routes unless it is a landing hub.
- Templates for models, benchmarks, providers, protocols, safety, and legal topics include limitations before recommendations.
- AI-assisted drafts stay draft until a human reviewer checks sources, support boundaries, and route/discovery impact.
Template-level lint checklist
| Check | Why it matters | Fix |
|---|---|---|
| Lead says the job of the page. | Readers and agents should know whether the page teaches, compares, governs, or records evidence. | Rewrite the first paragraph around the reader task. |
| Tables expose decisions. | Dense pages need scannable matrices, not only long prose. | Add decision, state, source, or failure-mode tables. |
| Examples are copyable. | Builders need prompts, folder trees, schemas, or procedures they can try. | Add a short concrete artifact with a done-means check. |
| Claims carry status. | Draft, source-needed, and reviewed claims should not look identical. | Add frontmatter, status panel text, or source notes. |
| Related pages are intentional. | The graph should route to the next useful page, not a generic footer pile. | Link architecture to operations, operations to schema, and schema to policy. |