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.
  • Language System — the authority chain from domain dialect to canonical DDL term, compressed notation, schema, and generated projection.
  • 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 because if the map lies, every later agent wastes thought. Truth state comes from preserved evidence, typed sources and frontmatter, claim state and verification dates, Git history, and generated-map checks. Private Stackmates receipts matter only when project delivery state is relevant.

The lead map for structure and names is Naming Standards. The Language System owns the terms those structures use. Knowledge Schema maps a new domain.

Read them before changing structure, names, categories, or cross-domain schema. Then use the other wiki maps to choose the page job, ownership mirror, tag projection, and reader route.

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​

  • depends-on Knowledge Schema — the method that keeps relationships, representation, validation, level, and review explicit.
  • applies-to Systems — the canonical area for modeling, controlling, improving, representing, and retaining systems knowledge.
  • pairs-with Standards — the rules these maps enforce.
  • proved-by Reality Scoreboard — the proof discipline the control plane reports into.
  • applies-to Sitemap — inspect the generated full route tree

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?

Changes my mind: a control-plane map that adds no routing value should leave the Spine rather than remain through habit.

Next question: Which map still makes the reader infer its authority or next action?