The status of a section and of a domain's header
The status of a section is built from the nodes under it that are no section: approved where every one of them is approved, and draft otherwise. The status of a domain's header is built the same way from every node of the domain but the header itself. Nobody approves a section or a header itself, nor a header's level and where its code is. The status is built anew after every change to the specification and never written by hand.
A section and a domain's header require nothing (§s-7445ahgjck2aefg, §s-ef93u6cnbs2sevr): what they state, the nodes under them state, so their own words leave an owner nothing to agree to. A header's level is one of those the project's own guidelines list (§s-nkyty4dy9x2v2a4), in a rule the specification's owners approve. Where its code is says where to look, not what must hold. Built from the nodes under it, the status shows at a glance which parts of the specification wait for their owners. Built anew after every change, it never falls behind those nodes (§s-kh8qcd5kxgh9z3j).
The links it makes
The links made to it
- cites ← What a node's status says
- cites ← Removal goes through the archive when an approval was ever given
- implements ← What is checked, when, and what a failure costs
- implements ← The commands
- cites ← The hooks
- implements ← Indexes, incoming links, gathered values and the statuses of sections and headers, rebuilt
- cites ← How an approval is recorded
The decisions taken on it
- Problem
A section and a domain's header were confirmed as a rule is, so their status claimed an agreement to words that require nothing, and said nothing of the nodes they hold.
- Ruling
The owner: their status is the state of what they hold, built and only shown, whatever the number of rules; their own wording is meta-information nobody approves.
The tests bound to it
- skills/tools/test/unit/model.test.ts · @spec s-9kfdycuq34beqvs builds a section's status from the nodes under it that are no section, and a domain's header's from every node of the domain
- skills/tools/test/unit/reindex.test.ts · @spec s-9kfdycuq34beqvs writes the status of each section and domain's header from the nodes under it, after every change
- skills/tools/test/unit/validate.test.ts · @spec s-9kfdycuq34beqvs refuses a section or a domain's header whose status is not the one the nodes under it produce