describe-laws-and-style

To separate project invariants from conventions, distinguish non-negotiable laws from evolvable style. This establishes a clear governance framework that prevents architectural drift across Phases, implementations, and refactors by enforcing laws while preserving conventions.

In project governance, laws represent non-negotiable invariants that must be strictly enforced, while style represents evolvable conventions that can be modified. Documenting these distinct roles prevents conflicts and clarifies responsibilities for maintaining architectural standards.

To codify laws and style for Ushabti-based projects, review and update the .ushabti/laws.md file for invariants and the .ushabti/style.md file for conventions. This documents governance rules to align project practices across implementations and refactors.

The Lawgiver is responsible for modifying laws (invariants), while the Artisan is responsible for modifying style (conventions). This role separation ensures non-negotiable invariants are enforced while allowing conventions to evolve without conflict.

Yes, you can audit project alignment by applying laws and style governance across Phases, implementations, and refactors. This ensures project practices adhere to codified invariants and conventions, preventing architectural drift in AI-assisted software development.

Enforce invariants during a refactor when non-negotiable laws are at risk of being violated, but update conventions when only evolvable style needs adjustment. This distinction preserves architectural integrity while allowing style to adapt without breaking governance rules.