SpecSheriffIn progress
rule · _guidelines/tools/7.2.8 · s-dbk2vyeg8z5jxna

Generated copies against the nodes

Checkedconfirmed by its owner

sheriff binding generates in memory the copies the nodes produce, and compares them with what is committed.

  • The copies are the files the technical appendix lists for the types and runtime checks (§s-pvzms7d8kxb8dk2), and those each of the project's own generators prints, run as sheriff types runs it (§s-km4x4s26kv7pjze).
  • Each copy is compared with what the last commit holds instead while a node it waits for is unchecked (§s-f5rz6b7dhxejjts). Each such node is reported.

It refuses:

  • a list of the files for the types and runtime checks naming a file of another extension or a path outside the repository;
  • a path a project's generator prints outside the repository or under specs/;
  • two rules of the stack each defining such a list;
  • a name that cannot be generated (§s-suv42g8r3ra2h6b);
  • a RecordType holding two fields of type variant, its inherited ones counted.

The links it makes

The links made to it

The decisions taken on it

2026-10-31 · textual
Problem

The row of generated copies did not name the refusal of a listed path that leaves the repository, which the tools make because each path of the list is taken from the root of the repository.

Ruling

Carrying out the owner's rule on where the generated files are written (§s-pvzms7d8kxb8dk2): the row names that refusal.

2026-10-31 · textual
Problem

The check compared each kept generated copy with what the nodes produce now, while code generated from the nodes now waits for them to be checked.

Ruling

Following the owner's ruling on §s-kh8qcd5kxgh9z3j: code generated from the nodes waits until every node it is generated from is checked, no commit changing it meanwhile, and its lag is reported.

2026-11-06 · textual
Problem

Every copy was compared with the last commit while any RecordType, any node a project's generator writes from or any rule listing a generator was unchecked, though each copy is generated from nodes of its own.

Ruling

Carrying out the owner's rule that what is generated waits for the nodes it is generated from (§s-kh8qcd5kxgh9z3j): each copy waits only for the nodes it is generated from, as sheriff types writes it (§s-f5rz6b7dhxejjts).

The work deferred on it

2026-11-06 · the agent, from a review of the code of the tools

Two of a project's generators, or a generator and the list of the files for the types and runtime checks, may print the same path; each copy is then compared with what one of them writes, and the mismatch never clears. Refuse a path printed twice.

The tests bound to it