Canonical rules-file ordering is writer-enforced, not hook-enforced #53
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#53
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
How does .dochygiene-rules.json stay visually grouped by lifetime tier so the human can read it without mentally sifting — a post-command hook, or something simpler?
Resolved: writer-enforced canonical ordering, no hook. Every code path that serializes .dochygiene-rules.json writes it grouped by lifetime tier (delete-once-served, temporary, keep;
nominationskey afterrules), sorted by glob within each group. Idempotent; no drift window between a command finishing and a hook firing; nothing besides the plugin writes the file today, and hand edits re-canonicalize on the next write. A post-command hook was considered and rejected as more moving parts for the same result. Decided in wayfinder charting 2026-07-15.