Rule Enforcement

Rule enforcement turns repository law, policy data, and generated evidence into actionable pass or fail decisions.

Enforcement Model

flowchart TD
    Rule[Repository rule] --> Policy[Load policy]
    Policy --> Execute[Execute check or enforcement logic]
    Execute --> Evidence[Produce evidence]
    Evidence --> Pass{Pass?}
    Pass -- No --> Violation[Emit violation and block or warn]
    Pass -- Yes --> Record[Record compliance]

This page should teach maintainers that enforcement is not only the final message. It is the full chain from rule source, to loaded policy, to executed logic, to evidence output, to a blocking or advisory decision.

Repository Anchors

• enforcement rule sources live under configs/sources/governance/governance/enforcement/
• the governance enforcement reference code lives in src/reference/governance_enforcement.rs
• governance and control-plane application logic consume those rule sets through the maintainer automation surface

Main Takeaway

Rule enforcement is where Atlas governance becomes operational. The rule source, the policy-loading path, the evidence artifact, and the final pass-or-fail decision all need to stay visible or the repository starts enforcing things no one can properly explain.