Part of #4.
What
Gate chant's own documentation against this repo's rule identifiers, so a subset change cannot leave chant's prose describing the old subset.
Why it is post-submission rather than now
It is maintenance rather than paper content. But it is the reason the split into two repos is safe at all, so it should not be dropped: chant's existing doc-parity gate (INTENTIUS/chant#1062) reads a doc that lives beside it, and if the normative text moves here, that gate no longer watches the thing that matters.
Without this, INTENTIUS/chant#2306 recurs across a repo boundary with nothing watching. That issue is three wrong claims in prose that a gate could not see; the failure mode is proven, not hypothetical.
Shape
chant's docs cite rule identifiers. A check — in chant's CI, consuming this repo's published spec — asserts every cited identifier exists at the spec version chant declares, and that chant's claims about a rule match the spec's.
Depends on
#33 (ownership decision), #18 (versioning, so chant can declare a version), and a published spec artifact (#23).
Part of #4.
What
Gate chant's own documentation against this repo's rule identifiers, so a subset change cannot leave chant's prose describing the old subset.
Why it is post-submission rather than now
It is maintenance rather than paper content. But it is the reason the split into two repos is safe at all, so it should not be dropped: chant's existing doc-parity gate (INTENTIUS/chant#1062) reads a doc that lives beside it, and if the normative text moves here, that gate no longer watches the thing that matters.
Without this, INTENTIUS/chant#2306 recurs across a repo boundary with nothing watching. That issue is three wrong claims in prose that a gate could not see; the failure mode is proven, not hypothetical.
Shape
chant's docs cite rule identifiers. A check — in chant's CI, consuming this repo's published spec — asserts every cited identifier exists at the spec version chant declares, and that chant's claims about a rule match the spec's.
Depends on
#33 (ownership decision), #18 (versioning, so chant can declare a version), and a published spec artifact (#23).