Skip to main content

Wiki Control Plane

Which map do you read before changing the playbook?

The Spine​

  • Wiki Schema — how the wiki runs: control plane, routing rules, the Map-First Edit contract, and the binding agent read order.
  • Wiki Index — the generated public spine: the shortest path into the system and the high-signal hubs.
  • Page Types — the page-job catalogue: choose the job before writing the body.
  • Domain Matrix — the faceted projection for cross-domain intersections.
  • Folder Ownership — the contract linking playbook folders, capabilities, and the skill domains that serve them.
  • Naming Standards — the System of Names authority; no name is minted without it.

Zoom Out​

This folder is the epistemic core of the playbook — the meta that defines the matter. Content pages teach; these maps define what exists, where it routes, and what each page's job is. They are held to a higher bar than ordinary content — only truth, route, owner, and next action — because if the map lies, every later agent wastes thought.

Context​

Questions​

What would an agent do differently after reading your maps first?

  • Which page of your wiki would mislead a cold reader today — and which map should have caught it?
  • If a skill and a folder disagree about who owns a method, where is the tie broken?