aboutsummaryrefslogtreecommitdiff
path: root/scripts/workflow-integrity.py
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-06-12 14:08:52 -0500
committerCraig Jennings <c@cjennings.net>2026-06-12 14:08:52 -0500
commit81395a7c8473fb2e0ad8239f02825c29288404e9 (patch)
tree835dc8d31152e47aa7affdb433eb7fc2d8eadb28 /scripts/workflow-integrity.py
parentfbeef0c83b15eb7a82cdb8c2b999e232e4f997b6 (diff)
downloadrulesets-81395a7c8473fb2e0ad8239f02825c29288404e9.tar.gz
rulesets-81395a7c8473fb2e0ad8239f02825c29288404e9.zip
docs(todo): require a per-project Priority Scheme header
Every project's task list now opens with a "[Projectname] Priority Scheme" section declaring both the [#A]-[#D] semantics and the tag vocabulary. The concept already lived in the tooling (task-audit enforces a declared tag set, process-inbox checks for the scheme before filing), but nothing required the section or fixed its name, so a list could leave [#A] and its tags undefined. The set is declared, not fixed. A project adapts the priorities and tags to its own work. The floor is that both are spelled out.
Diffstat (limited to 'scripts/workflow-integrity.py')
0 files changed, 0 insertions, 0 deletions