Checked means its owner confirmed its present wording
A node's status is empty or checked. Checked means that the node's owner (§s-67vekyup7y8smap) confirmed its present wording — its title, text and reason, and the values its kind carries beside them, such as the fields of a data record node.
Any change to that wording, the owner's own included, leaves the node unchecked until its owner confirms the new wording, and so does a move or a change that gives it another owner. So does a withdrawal of its confirmation, which anyone may make, outside the SpecSheriff guidelines a project takes (§s-bsya3febm6u64ab), and which names whoever made it.
A change to its links or its metadata leaves the status as it is.
A checked status claims that the node's owner agreed to what it now states. A status that survived a rewrite would certify words nobody confirmed, and one that survived a change of owner would certify them in the name of someone who never agreed to them.
Links and metadata are not what an owner confirmed, and they change as the specification grows around a rule.
A withdrawal gives no agreement in anyone's name: it only leaves a node unchecked, as a change to its wording by anyone does, so whoever finds a confirmed rule wrong can keep any further change to its code or its tests from being committed (§s-utvqbypzhmgndug) without waiting for its owner; naming them tells the owner whom to ask.
Its list
- Of
- the values a node's status can take
- Declared in
- specs/_schema/node.schema.json
#/$defs/status
"""checked"
The links it makes
The links made to it
The decisions taken on it
- Problem
A data record node holds its fields apart from its text (s-e877bnfa559tvk9), and a field changed would have left the status standing over a structure the owner never confirmed.
- Ruling
The owner: a data record node's fields are part of the wording a confirmation covers.
- Problem
A kind of node came to carry values beside its text, and a value changed would have left the status standing over values the owner never confirmed.
- Ruling
The owner: the values a node's kind carries beside its text are part of the wording a confirmation covers, as a data record node's fields are.
- Problem
One person confirmed every node, and the values a confirmation covered were listed by the kinds of node one project uses.
- Ruling
The owner: an owner of the part a node stands in confirms it (§s-67vekyup7y8smap), and a confirmation covers whatever values the node's kind carries beside its text. An owner's own change to a wording needs a new confirmation as anyone else's does, since the fingerprint of the wording, not who changed it, decides.
- Problem
A move was said to leave the status as it is, while only a node's owner confirms it, so a node moved under another owner stood checked over words that owner never read.
- Ruling
The owner: checked means the node's owner confirmed its present wording; a move or a change that gives the node another owner empties its status.
- Problem
The reason held that a checked status claims its owner read the words a node holds, while a node may now be confirmed in its owner's name where its change states nothing new.
- Ruling
Following the owner's ruling on §s-67vekyup7y8smap: a checked status claims the owner agreed to what the node states.
- Problem
No rule said who may withdraw a confirmation, while the procedure let anyone.
- Ruling
The owner: anyone may withdraw a confirmation, and the withdrawal names whoever made it; the SpecSheriff guidelines a project takes stay as they were confirmed where they are written (§s-bsya3febm6u64ab).
The tests bound to it
- skills/tools/test/unit/reindex.test.ts · s-5ah25f6gy99panq empties the status of a checked node whose wording its owner has not confirmed
- skills/tools/test/unit/reindex.test.ts · s-5ah25f6gy99panq empties the status of a node confirmed by someone who is not its owner