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.

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
loop_phase: capture
level: working

Shape

1. Define the territory boundary.
2. Name the main axes.
3. Map the players, platforms, processes, or forces.
4. Show the choice logic.
5. Route into deeper pages.
6. Name the visible gap.

Skeleton

TITLE

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?

Checks

• The page maps a field instead of teaching one node.
• The boundary is clear.
• Axes explain why items are grouped.
• Routes help the reader choose a next move.

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?