Only its owner confirms a node
The specification has one owner. A domain (§s-yggv9myedprnaa7) or a section may have an owner of its own, who takes the place of the owner above for every node within it.
A node is confirmed by its owner and by nobody else, and a confirmation names the owner. The exception is a node whose wording changes only to state what its owner confirmed in another node, or only by a replacement that changes no meaning, such as a renamed term or path: the agent that made the change, working for that owner, confirms it in the owner's name, as the owner's confirmation, and reports it to the owner, who may withdraw it.
A confirmation means that whoever answers for a rule has agreed to what it states, so it is that person's to give. Owners of domains and sections divide the reading as the specification is divided, so that it can grow beyond what one person reads.
A node whose wording only states what its owner confirmed in another node asks nothing its owner has not agreed to, and a replacement that changes no meaning states nothing new; shown again, either would spend the owner's attention on no decision. An agent working for the owner already acts in the owner's name and reports to the owner as it works: the report lets the owner see that the change was only that, and withdraw the confirmation where it was not.
The links it makes
The links made to it
- cites ← Checked means its owner confirmed its present wording
- cites ← Removal goes through the archive when the node was ever confirmed
- cites ← A domain's specification opens with its header
- implements ← What is checked, when, and what a failure costs
- cites ← Where an agent writes, the checks run at each of its edits
- implements ← Where the files are
- implements ← How a confirmation is recorded
The decisions taken on it
- Problem
One owner confirmed every node, which binds a growing specification to one person, and the confirmations were kept outside the specification, where nobody else could check them.
- Ruling
The owner: a domain may name its owners in its header; a confirmation names who gave it, beside the fingerprint of the wording, is kept with the specification and is accepted only under that owner's signature. A confirmation read off the approvals of a merge request was declined, since it would tie what a status means to one hosting platform.
- Problem
Owners could be named on a domain's header alone, and a confirmation was to carry its owner's signature, made with a key no agent can use.
- Ruling
The owner: the specification has one owner, and a domain or a section may have its own, taken as a task is taken, oneself included; a confirmation names its owner and carries no signature, the agent's hooks guarding the status.
- Problem
The spec-review skill had the agent confirm, unshown, a node changed only to state what its owner had confirmed in another node, or by a replacement changing no meaning, while this rule let nobody but the owner confirm a node.
- Ruling
The owner: such a node is confirmed in its owner's name by the agent that made the change for that owner, which reports the confirmation to the owner; the owner may withdraw it. The owner amended the principle that nothing unconfirmed is implemented to the same effect.
The tests bound to it
- skills/tools/test/unit/confirm.test.ts · s-67vekyup7y8smap refuses a node whose owner is someone else, naming that owner, and confirms none of those named
- skills/tools/test/unit/model.test.ts · s-67vekyup7y8smap names no owner where the specification names none
- skills/tools/test/unit/model.test.ts · s-67vekyup7y8smap takes a node's owner from the nearest section or header naming one, else the specification's