Residual assessments live in a nominations key in .dochygiene-rules.json; rejects block exact repeats only #52
Labels
No Label
P0
P1
P2
P3
afk-ready
hitl
next
ready-for-agent
review
semi
waiting
wayfinder:grilling
wayfinder:map
wayfinder:research
wayfinder:task
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: jared/cc-os#52
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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
Where do the non-rule-shaped assessment records (rejected nominations, open consults) live, and what exactly does a persisted rejection block in future runs?
Resolved: same file, second top-level key
nominations(no sibling artifact — one file to read, slurp, and discuss). Holds rejected nominations and open consults; never touches the file filter (rules alone filter files).What a rejection blocks — exact repeats only. Worked example: judge rejects
docs/research/** -> temporary('findings docs, not disposable output'). Next run, haiku re-proposing exactlydocs/research/** -> temporaryis dropped at nomination intake, before the judge. Butdocs/research/** -> keep(different lifetime) ordocs/research/drafts/** -> temporary(narrower glob) flow through normally, with the past rejection + its why injected as judge context. Rejections may carry a consider-instead pointer (the judge's amend verdict). Escape hatch for stale rejections: hand-delete the entry (removals stay HITL with recorded reasoning).Consults are the opposite of a filter — a pending-human queue that must resurface each run until answered. Decided in wayfinder charting 2026-07-15; schema detail -> #56.