chore(governance): declare legitimate root entries - #35
Conversation
The `estate-rules` gate reports every tracked root entry absent from .machine_readable/root-allow.txt, and offers two cures: move the entry into a subdirectory, or add it here with a justification. Declaring is the right cure here. The allowlist derives from the RSR template's "Proposed Final Directory Map", which anticipates a documentation repository — so genuinely correct top-level directories are reported as drift. Moving them would break every path that references them in order to satisfy a map that was never written for this project's shape. Entries were read from the gate's own output rather than from a directory listing, so this adds exactly what is failing and no more — an allowlist wider than the finding would be a blind spot. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
|
|
Note Automatic reviews are paused because your trial's included automatic processing has been used for this period. Upgrade now, or comment "Gitar review" to run a review anytime. Code Review ✅ ApprovedDeclares eight legitimate root entries in the allowlist to satisfy the estate-rules gate. No issues found.
OptionsDisplay: compact → Showing less information. Comment with these commands to change the behavior for this request:
Important Your trial ends in 4 days — upgrade now to keep code review, CI analysis, auto-apply, custom automations, and more. Was this helpful? React with 👍 / 👎 | Gitar |
|
|
1 participant
The
estate-rulesgate reports every tracked root entry absent from.machine_readable/root-allow.txt, offering two cures: move the entry into a subdirectory, or add it here with a justification.Declaring is the right cure. The allowlist derives from the RSR template's "Proposed Final Directory Map", which anticipates a documentation repository — so genuinely correct top-level directories (
crates/,daemon/,compiler-core/) are reported as drift. Moving them would break every path that references them, to satisfy a map never written for this project's shape.Worth noting at source: across the 16 repositories failing this gate,
REQUIRES_INITIALISATION.mdappears in 12 and.githooks/in 9. Those are files the RSR template itself ships — the template's own allowlist omits files the template creates, so a freshly minted repo fails this gate on day one. That is a template defect worth fixing upstream as well.Entries were read from the gate's own output rather than a directory listing, so this adds exactly what is failing and no more — an allowlist wider than the finding would be a blind spot.
🤖 Generated with Claude Code