Templates keep the wiki from drifting into unstructured essays. The new handbook pages use docs-style templates for architecture, how-to, operations, schema, examples, and source-backed case studies.
Architecture Guide
Problem, system boundary, folder or service shape, tradeoffs, failure modes, and next implementation step.
How-To Tutorial
Prerequisites, exact procedure, copyable prompt or command, expected output, and done-means checklist.
Operations Runbook
Trigger, inputs, steps, severity, rollback path, checks, log entry, and escalation rule.
Schema Page
Rule purpose, required fields, allowed values, examples, lint checks, and context-pollution warning.
Example Build
Audience, folder tree, operating rhythm, prompts, roles, policies, and scale-up notes.
Navigation Mechanic
Routing file shape, update rule, query algorithm, failure mode, and search-upgrade threshold.
Concept
Definition, why it matters, common confusions, related standards, examples, related pages.
Protocol
Summary, when to use, when not to use, core fields, examples, validator behavior, comparisons.
Comparison
Summary judgment, quick table, decision tree, detailed criteria, use-together pattern, sources.
Model Profile
Overview, modalities, capability profile, benchmarks, architecture, deployment, interop readiness, limits.
Benchmark
What it measures, why it matters, limitations, leaderboard source, update cadence, related models.
Implementation Tool
What it does, supported inputs, workflows, common errors, code examples, related standards.