Gathered values stand beside their field
Where the values of a field of type one of are gathered from elsewhere in the specification, all of them are written beside the field, each with the node it comes from. They are gathered anew after every change to the specification and never written by hand.
Beside the field, its values are read whole where the field is described, without searching the parts they come from (§s-k73czmpkazcx7mu), and the node each comes from tells whom to ask about it. Gathered anew after every change, they never fall behind their source, as a list kept by hand would (§s-kh8qcd5kxgh9z3j).
The links it makes
The links made to it
- cites ← Checked means its owner confirmed its present wording
- implements ← What is checked, when, and what a failure costs
- implements ← The commands
- implements ← What the export, the guide and
sheriff showwrite of a node - implements ← Indexes, incoming links and gathered values, rebuilt
- cites ← The type each neutral type of a field gives
The decisions taken on it
- Problem
The values gathered for a field from the domains were held only in memory, by the checks and the generated types, so a reader of the field saw none of them where it is described.
- Ruling
The owner: what a procedure gathers is written into one place at once, the procedure giving the current list at every run; the values a field gathers from elsewhere in the specification are written beside the field, each with the node it comes from, gathered anew after every change, never written by hand, and no part of the wording a confirmation covers, so a domain adding a value leaves a data record of contracts checked.
The tests bound to it
- skills/tools/test/unit/reindex.test.ts · s-ju5vcanbjph7mgh writes beside a field the values gathered from its source, each with the node it comes from, and none beside a field holding its own list