What does setting a repository or organization ruleset enforcement status to 'Evaluate' (or equivalent non-enforcing mode) allow administrators to do?

Rulesets support enforcement modes that include active enforcement and evaluate/dry-run style operation depending on product wording. Evaluate lets administrators measure how often rules would fail and which actors would be affected without hard-blocking merges or pushes yet. That de-risks rollout of strict policies such as required linear history, signed commits, or restricted paths. Evaluate is not a secret scanning bypass, does not auto-delete branch history, and does not disable two-factor authentication. After reviewing insights, owners should communicate policy, fix workflows, then enable full enforcement and manage bypass lists carefully for break-glass roles.