Keep verdicts persist as keep rules; exact-path singleton keeps allowed #51
Labels
No labels
P0
P1
P2
P3
bug
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#51
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Map: #49
Question
Should judge "keep" assessments become normal keep rules in .dochygiene-rules.json, or live in a separate assessments artifact — and what about single files that don't generalize to a pattern?
Resolved: reuse keep rules — no separate assessments artifact for keeps. A judge 'keep' verdict persists as a normal
lifetime: keeprule (glob + note) in the existingrulesarray; matched = managed already removes covered files from the calibrate pool, and staleness is free (the glob covers future files like any rule). Singleton files judged fine persist as exact-path keep entries — e.g.{ "glob": "docs/research/clutter-pattern-inventory.md", "lifetime": "keep", ... }. This requires a scoped relaxation of the 'rule is the CLASS, never the PATH' quality test: it exists to prevent bad DELETION rules, so exact-path/instance globs become allowed for keep-tier entries only, and stay forbidden for temporary/delete-once-served. Decided in wayfinder charting 2026-07-15.