The structure of the specification is defined by its schema
The structure of every node and every file of the specification is defined by its schema. A file that does not match the schema is refused, and the refusal names the field that is wrong. Why each part of the structure is as it is, is written in the schema beside it.
A structure stated in prose can be broken without anyone noticing; stated as a schema that every file is checked against, it cannot. The schema is therefore the only description of the structure, and a rule that names a part of it, to say what that part means, is compared with it by machine.
The links it makes
The links made to it
The decisions taken on it
- Problem
The rule named the files the schema is kept in, which is the layout of one toolset rather than what the specification requires.
- Ruling
The owner: the guidelines apply the split between base and appendix to themselves (§s-a4rbry4hsu34hy8); where the schema is kept is described in the appendix of the tools.
The tests bound to it
- skills/tools/test/unit/schema.test.ts · s-eferktypcj7njt5 accepts ${what}
- skills/tools/test/unit/schema.test.ts · s-eferktypcj7njt5 accepts every file of the specification as it stands
- skills/tools/test/unit/schema.test.ts · s-eferktypcj7njt5 names a field nobody declared, and a required field that is missing
- skills/tools/test/unit/schema.test.ts · s-eferktypcj7njt5 names the field that is wrong
- skills/tools/test/unit/schema.test.ts · s-eferktypcj7njt5 refuses ${what}