Wiki Schema

This page defines where knowledge goes and how agents should maintain the wiki.

Routing Rules

Content type	Destination	Rule
Public reusable know-how	`/docs/**`	Explain it so a future human or agent can reuse it
Public argument or narrative	`/meta/**`	Use when the job is persuasion, timing, or story
Canonical language	`src/pages/agents/**`	Update DDL for terms; update DML for compressed agent notation
Private plans and delivery state	`drmg` CLI	Keep project-specific demand, decisions, traces, and status out of docs
Raw or unresolved ideas	`.FLOW/**`	Process toward docs, language, demand, or deletion
Engineering implementation	`/home/wik/code/sm/stackmates`	Build product and platform changes there

Type	Job	Required shape
`hub`	Orient a section	What it is, start paths, core links
`concept`	Explain one reusable idea	Definition, why it matters, when to use, links
`playbook`	Guide repeatable action	Trigger, steps, outputs, checks
`domain-map`	Explain a territory	Value chain, players, forces, useful questions
`evidence`	Preserve source-backed claims	Claim, source trail, confidence, implication
`glossary`	Clarify language	Canonical term, aliases, contrast, DDL link
`decision-record`	Explain a public architectural decision	Context, decision, consequences, date

New or materially revised docs should include:

---
title: Clear Title
sidebar_label: Short Label
description: "One sentence that explains the page job."
tags:
  - Wiki
  - Relevant Topic
---

Use description as the answer-engine summary. Keep titles human-readable and avoid local shorthand unless the page defines it.

Claims based on external facts need a Sources, Links, Context, or Source Trail section.
Interpretation is allowed, but it should not pretend to be raw evidence.
Private project state can inform a page, but the page must stand alone without exposing private details.
.FLOW paths may be named only when explaining the operating system itself; do not use .FLOW as reader-facing provenance for an idea.

Operation	Purpose	Output
`ingest`	Turn raw signal into durable knowledge	`/docs`, `/agents`, CLI demand, or deletion
`query`	Answer from durable sources first	Cite `/docs`; use CLI only for private/project state
`lint`	Detect drift and broken structure	Findings for links, language homes, orphans, and source gaps
`promote`	Preserve reusable answers	A public doc, DDL term, DML token, or CLI trace

DDL lives at /agents/ddl-nomenclature. DML lives at /agents/dreamineering-symbols.

When a concept becomes reusable: