scripts/elicitation-provenance.mjs
the provenance ledger stays honest - every required point has a row, a deferred answer names a backlog row that exists, and a point stops being legally pending once something it gates has been written; and the guard itself reached a commit before any Gate artifact it protects did
Reference
- Status. Required - part of the
coreprofile. - How it arrives.
copy- ship verbatim; the repo gets a byte-for-byte copy (guards, templates that carry no repo-specific content) - Shipped form. read it in the standard's own tree
The rule that requires it
Every point this standard asks about MUST be answered through a mechanism
What checks it
node scripts/elicitation-provenance.mjs- the record of who answered what is present and internally consistent, and the guard that produced it landed before any Gate artifact it protects did Blocks the build when it fails.
