A specification is put live once
A rule of the project's own guidelines states that the specification is live; without it, the specification is a draft. A project taking up the method with code it already has starts without that rule, and one starting without code starts with it. A commit adding the rule is refused unless the rule is checked in it and no symbol of the system's code outside its tests is left without a tag, and a commit removing the rule is refused.
The rule's owner confirms it (§s-67vekyup7y8smap), so the specification goes live only by that owner's act. Put live while code is untagged, it would refuse the next commit for code that commit did not touch. A live specification is revised under the ordinary rules, which let code tagged against an earlier wording stand (§s-kgbzk2ph9e6jfb4), so it needs no way back. A project without code has nothing to tag; one with code needs the draft for the reason §s-kkbqcb9xrpaepwn gives.
The links it makes
The links made to it
The decisions taken on it
- Problem
Nothing said how a specification passes from a draft to live, nor who puts it there.
- Ruling
The owner: one marker for the whole project, set as the project takes up the method, put live by the owner, once and one way, refused while code is untagged; held as a rule of the project's own guidelines rather than a value beside the owner, since a confirmation covers a rule and no such value.
- Problem
The system's code came to include its tests, which carry a sid rather than a tag.
- Ruling
Following the owner's ruling on §s-hheus6f395ynqvc: no symbol of the system's code outside its tests is left without a tag.