The map is a mindmap of the specification
The map is the specification seen from above: a mindmap drawn from the nodes each time it is built, holding no fact of its own. It shows the structure and nothing else — a domain, the parts under it, then the rules, down to the individual rule — from the nesting, the titles and the level of each domain alone. A branch opens and closes, so a reader goes to the part they came for while the whole stays in view around it. The branches read: the guidelines first, then contracts, then a branch for each level of the domains, from the top, holding its domains in the order §s-uw9n84edf7cbe9n gives, and the technical appendix last.
A specification is read one rule at a time and has to be understood as a whole, and the two pull against each other: the full text is more than anyone holds at once, and an extract loses where the rule sits. A mindmap answers both — the shape of everything, and the detail of whatever is opened. Drawn from the nodes at each build rather than kept beside them, because a diagram kept apart is a second copy of the specification and disagrees with it silently. The levels and the order of the domains carry how the domains bear on one another.
The links it makes
The links made to it
The tests bound to it
- skills/tools/test/unit/generated.test.ts · s-zu8ne3wq84zchc4 the map reads guidelines, contracts, a branch per level from the top with its domains in order, the technical appendix last
- skills/tools/test/unit/generated.test.ts · s-zu8ne3wq84zchc4 the map shows titles and nesting only, nothing of a rule's text