---
type: reference
title: Domain docs layout and consumer rules
description: Single-context domain documentation for dank/command-center — glossary and ADRs live inside the omp-docs knowledge base, not at the repo root.
tags:
  - skills
  - documentation
  - okf
  - agents
timestamp: 2026-10-20
---

# Domain docs: single-context, inside the KB

One domain, one glossary, one ADR folder — and all of it inside the existing
knowledge base, because this repo caps its root at "config, docs, scripts,
harness dirs" and `omp-docs/` is the one knowledge base. A `docs/` tree at the
repo root would be a second KB with a second set of index rules, which is exactly
how documentation starts disagreeing with itself.

| Kind | Path | Status |
|---|---|---|
| Glossary | `omp-docs/glossary.md` | deliberately not created yet |
| ADRs | `omp-docs/decisions/NNN-<slug>.md`, listed by its `index.md` | directory exists, empty |
| Facts | the rest of `omp-docs/` | existing concept pages own them |

## Consumer rules

1. Read [the KB index](/index.md), then the relevant directory's `index.md`, then
   the concept page. That is AGENTS.md's existing discipline; the engineering
   skills follow it instead of inventing a second entry point.
2. Read the ADRs that govern an area before changing that area, and write one the
   moment a decision stops being reversible. An ADR records the choice, the
   reasons, and what was rejected — the part that stops a later agent from
   re-litigating it.
3. Do not confuse the neighbours. [Research](/research/index.md) is decision
   *support* and explicitly not fact. [log.md](/log.md) is chronology, where
   incident lessons land before settling into concept pages. An ADR is neither: it
   is the decision itself, dated, and it stays true after the code moves on.
4. One fact, one owner. If a glossary term or an ADR sentence restates a concept
   page, the concept page wins and the duplicate is deleted.

## Why the glossary is withheld

A glossary earns its bytes when it holds terms no other page owns. The obvious
candidates already have owners: host roles in [system](/system/index.md), agent
configuration in [core](/core/index.md), skill tiers in
[skills](/skills/index.md). A term list that paraphrases those is a second owner
of facts already written down, and the first thing to go stale. Create
`omp-docs/glossary.md` when a real term has nowhere else to live, and list it in
the KB index the same commit you create it.