Repository navigation
Distinguish requirement provenance from central-admission origin - #643
Conversation
Signed-off-by: transitrix <automation@transitrix.com>
Signed-off-by: transitrix <automation@transitrix.com>
|
Independent exact-head review completed at |
|
Correction to the preceding review note: the exact reviewed and merged PR head is |
What changed
Local REQUIREMENT records may use
origin: legislative,process-product, orproject-productwithout BIND-005. Central-admission maps, other element types, and unrecognised or ambiguous origin values retain the error. The binding contract documents the distinction and the bounded scalar reader; authored field names and shapes remain unchanged.How it is verified
repo-checkCLI controls pass against source and a locally packed consumer with companion vocabulary files. BIND-001 through BIND-004 and legacy boolean inputs remain covered.Checklist
main, one concern per PR.