fehmEngineering practices
A boundary worth
making visible.
Review how the code changes against the decisions your team has made.
Controller→Service→Database
Example: approved dependency direction
Architecture drift
A new import can cross an approved layer boundary. Fehm identifies the relationship and the rule it conflicts with. Resolving another violation does not conceal a new one.
Practice drift
A test, CI configuration, or other control can disappear from the evidence recorded in a baseline. Fehm reports the lost signal so it can be reviewed.
Approve the rules you need.
Terminal
fehm practices audit
fehm practices propose --profile auto
# Review .fehm/practices.proposed.json
fehm practices approve
fehm practices baseline31 static signals cover common software and AI engineering concerns. They support review without claiming standards compliance. Choose required rules, warnings, and reasoned exemptions for your project.
Read the policy and drift guide →