Domain Map Template
What makes a territory easier to choose inside?
A domain-map page shows the terrain before the reader chooses where to act.
The reusable model is boundary -> axes -> map -> choice logic -> routes -> gaps. Apply it when the reader must choose inside a territory before learning one node in depth.
Use this when the page job is domain-map.
Frontmatter
type: domain-map
template: domain-map-template
template_url: /playbook/standards/templates/domain-map-template
claim_state: REALITY | DREAM | CONSUMED
retrieval_trigger: "When should a future human or agent pull this map?"
loop_phase: capture
level: working
Shape
- Open with the problem.
- Ask the question the map answers.
- Name the decision this map improves.
- Define the territory boundary.
- Name the main axes.
- Map the players, platforms, processes, or forces.
- Show the choice logic.
- Route into deeper pages.
- Name the visible gap.
- Close with the falsifier and next question.
Skeleton
TITLE
Problem: WHAT TERRITORY IS UNCLEAR?
Question: WHAT MUST THE READER CHOOSE?
Decision: WHAT ROUTE OR PRIORITY GETS BETTER?
This map covers TERRITORY so the reader can choose ACTION.
## Boundary
What is inside this map, and what is outside it?
## Axes
- Axis A
- Axis B
- Axis C
## Map
What nodes, players, forces, or options matter?
## Choice Logic
How should the reader choose a route?
## Routes
- [Route A](/playbook/) - why this route matters.
## Gaps
What is missing, uncertain, or under-instrumented?
Changes my mind: What evidence would redraw this map?
## Retrieval
When should a future human or agent pull this map?
Version delta: What territory, route, or relationship changed in this update?
## Context
- [Related page](/playbook/)
## Questions
Next question: What constraint should the next loop inspect?
Checks
- The page maps a field instead of teaching one node.
- The first screen names the problem, question, decision, and territory.
- The boundary is clear.
- Axes explain why items are grouped.
- Routes help the reader choose a next move.
claim_state,retrieval_trigger,Changes my mind, andNext questionare visible.
Failure Modes
- The page becomes a flat catalog.
- The page explains one concept and forgets the field.
- The page lists options without choice logic.
Context
- Page Types - full page-type catalogue.
- Information Architecture Standard - placement and grouping rules.
- Perspective - map the view before choosing the route.
Questions
What choice should this map make easier?
- Where does the territory start and stop?
- Which axes explain the grouping?
- What route should the reader take next?
- What evidence would redraw the map?