Make .revealui the first-party RevDev root policy - #498
Merged
Merged
Conversation
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
2 participants
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.
RevDev currently tracks its fleet policy in a root
.claudetree, so the first-party rules and their CI admission depend on a vendor path. This change materializes the maintained 14-rule fleet profile under.revealui/content/rules, removes the tracked.claudedirectory, and makes the native manifest the default lockstep input. The gate rejects missing or empty native policy, Claude source provenance, edited rules, and tracked vendor copies.The project guide now lives at
.revealui/README.md, withAGENTS.mdand a thinCLAUDE.mdadapter pointing to it. Repository documentation links follow the native guide. The companion RevCon PR #153 provides the canonical first-party profile and linker behavior; review it before merging this PR.Validation: frozen pnpm install; 16/16 focused lockstep tests; both RevDev and RevCon native lockstep verifiers pass all 14 materialized rules; Biome, documentation lint, shell syntax, and diff checks pass. No merge or deployment performed.