Canonical rules-file ordering is writer-enforced, not hook-enforced #53

Closed
opened 2026-07-15 16:01:41 +00:00 by jared · 1 comment
Owner

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?

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?
jared added the
wayfinder:grilling
label 2026-07-15 16:01:41 +00:00
Author
Owner

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; nominations key after rules), 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.

**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; `nominations` key after `rules`), 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.
jared closed this issue 2026-07-15 16:05:22 +00:00
Sign in to join this conversation.
No description provided.