chore(governance): declare legitimate root entries - #35
Merged
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>
This comment has been minimized.
This comment has been minimized.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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