A project's own kind of node is numbered, counted and implemented as a rule is
The nodes of a project's own kind, declared in the extension of the schema (§s-eferktypcj7njt5), are numbered as rules are (§s-kag2m9tzdnduxdx) and count as rules of the section they stand in (§s-7445ahgjck2aefg). Unless the extension declares that they need no code, which exempts them from being implemented (§s-6fw72j65jkqrfpf), they are implemented and tested as a rule is (§s-6fw72j65jkqrfpf, §s-rah8b37kytb682y).
A rule of the project's own guidelines, refining this one, lists each such kind with whether its nodes need code, and the list names the extension as its declaration, against which the check of lists compares it (§s-jau82aq9juv9zzh).
A project needs kinds of node the SpecSheriff guidelines cannot foresee, and most are one more kind of requirement, so a kind is held as a rule is unless declared otherwise, and no check meets a node whose duties nobody stated. A kind whose nodes need no code is exempted once, for all its nodes; listed in a rule of the project's own guidelines, it is confirmed by the specification's owner, as every exemption is (§s-6fw72j65jkqrfpf).
The links it makes
- cites → The structure of the specification is defined by its schema
- cites → A node is cited by its sid, and its location names where it is in the specification
- cites → A node is one rule, and a section holds rules
- cites → A checked rule is implemented or exempted
- cites → The test comes before the code
- cites → What is checked, when, and what a failure costs
The links made to it
- cites ← The structure of the specification is defined by its schema
- cites ← A node is one rule, and a section holds rules
- cites ← A node is cited by its sid, and its location names where it is in the specification
- cites ← A project's own guidelines refine or implement the SpecSheriff guidelines
- cites ← A link carries its type
- cites ← The test comes before the code
- cites ← A checked rule is implemented or exempted
- cites ← The reviewer sees only the change and the nodes it names
- cites ← Where an agent writes, the checks run at each of its edits
- implements ← A checked node without code or a test
The decisions taken on it
- Problem
A project's own rules needed kinds of node the schema did not admit, and the rulings of 2026-10-31 had made the kinds of node the same in every project.
- Ruling
The owner: a project declares kinds of its own in the extension of the schema, each held as a rule is unless its nodes need no code. Whether a test is owed belongs to the code, written or generated, not to the kind, so the kind needs no more; no kind of container, since a section, to which the extension may add fields, groups nodes; each kind listed in a rule of the project's own guidelines, which its owner confirms.
The tests bound to it
- skills/tools/test/unit/binding.test.ts · s-vsh384ybt4w25a2 reports a checked node of a project's own kind that needs code and has none, but not one that needs no code, and lets a test carry its sid
- skills/tools/test/unit/model.test.ts · s-vsh384ybt4w25a2 numbers the nodes of a project's own kind among the rules of their section
- skills/tools/test/unit/validate.test.ts · s-vsh384ybt4w25a2 counts a node of a project's own kind as a rule of its section, and lets an exempts link reach it