A domain's specification opens with its header
A domain's specification opens with its header: a node stating what the domain does, its owner where it names one (§s-67vekyup7y8smap), the level it stands at and where its code is, whose consumes links name the sections of other domains the domain uses. The header also carries the index of the domain's sections — each one's sid, title and text, the text of a section stating what that section is responsible for, and the domains that use it — built from the sections and never written by hand.
Whoever works on one domain loads its header and learns from it alone what the domain is responsible for, who answers for its wording, how it is divided and what it takes from the others, without loading the rest. The index is built rather than written, because a table of contents kept by hand is a second copy of the sections and drifts from them.
The links it makes
The links made to it
The decisions taken on it
- Problem
The owners of a domain had nowhere to be named.
- Ruling
The owner: the header names them (§s-67vekyup7y8smap).
- Problem
Whether a domain may leave its header out, and whether a section has a header of its own, as a node of service carrying its metadata.
- Ruling
The owner: every domain opens with its header, which alone gives it its level, and so its place on the map and in the order of the domains; a section has none, since its own text says what it is responsible for and it names its own owner.
The tests bound to it
- skills/tools/test/unit/reindex.test.ts · s-yggv9myedprnaa7 names in a header's index the headers of the domains using a section
- skills/tools/test/unit/reindex.test.ts · s-yggv9myedprnaa7 rebuilds the index in a domain's header from the domain's sections