rules-normalize

You can normalize implicit project conventions like linters and style guides into explicit, structured GAAI rule files. This standardizes scattered standards into machine-checkable formats for consistent governance across your project.

Bootstrapping governance rules involves translating your team's preferred standards into standard GAAI rule files. This process classifies conventions by domain and verifies them against existing rules to prevent duplication and contradiction.

Yes, modifying existing rule files includes verifying them against current rules to ensure integrity. The normalization process checks for duplication and contradiction, maintaining governance coverage and GAAI standard compliance.

To ensure style guides and security policies follow GAAI standards, translate them into the standard GAAI rule format. This requires classification by domain and verification to maintain explicit, machine-checkable governance coverage.

No dependencies are required to normalize project conventions into rule files. The process works independently to classify your existing standards by domain and translate them into structured, machine-checkable GAAI rule formats.

You should use convention normalization when setting up governance for new projects, onboarding existing ones, or creating new rule files. It converts scattered linters and policies into explicit, structured rules the AI can enforce.