Skip to main content

Wiki Control Plane

Which map do you read before changing the playbook?

The Spine​

  • Naming Standards — the lead System of Names authority for folder structure, route names, filenames, skill names, generated projections, and business knowledge categories.
  • Knowledge Schema — the schema method for mapping unfamiliar domains into governed knowledge architecture: reality, evidence, structure, naming, value, agents, flow, controls, representation, and level.
  • 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.
  • Sitemap — the generated full route tree for finding any Playbook page by folder path.
  • Tags — the faceted public tag index for finding pages by concept.
  • Page Types — the page-job catalogue: choose the job before writing the body.
  • Domain Matrix — the faceted projection for cross-domain intersections.
  • Tag Taxonomy — the controlled vocabulary for explicit playbook frontmatter tags.
  • Folder Ownership — the contract linking playbook folders, capabilities, and the skill domains that serve them.

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. This wiki is the downstream exit of a one-way processing system: raw signal is refined upstream and lands here as durable knowledge, and the truth-state border ledger (.EVOLVE/wiki-log.md) is its epistemology layer — a claim with no entry there has no verified truth-state.

The lead map for structure and names is Naming Standards. The lead map for learning a new domain fast enough to build with it is Knowledge Schema. Use them before changing folder structure, route names, filenames, skill names, business knowledge categories, or cross-domain schema. Use the other wiki maps after that to choose page job, ownership mirror, tag projection, and reader-facing navigation.

The control plane also preserves situational wisdom. When a re-org resolves a repeated ambiguity, do not leave the lesson trapped in the diff. Update the naming rule, folder ownership map, or page-job contract so the next agent can choose the right action from context.

Context​

  • Standards — the rules these maps enforce
  • Start Here — the human orientation path into the wiki
  • Sitemap — the generated full route tree
  • Tags — public tag index
  • Glossary — canonical public vocabulary
  • Reality Scoreboard — the proof discipline the control plane reports into

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?