Deferred from the v0.9.3 pre-release review.
Current behavior
--force-tier works in every mode including gate. Nothing prevents an author from shipping altimate review --force-tier=trivial --mode gate in a production GitHub Actions workflow, effectively bypassing the classifier's gate. The bypass is visible in the signed envelope and in the PR-comment headline, but is not blocked.
Gap
Administrators enforcing SOX/SOC2 change management have no mechanism to disable the escape hatch on the production path. The flag is marked [EXPERIMENTAL / bench debug] in --help, but that is advisory text, not enforcement.
Proposal
Add a .altimate/review.yml option (name TBD, e.g. disableForceTierInGate: true) that causes --force-tier to error out with a non-zero exit when combined with --mode gate. Local and bench runs are unaffected. Config option precedence: CLI flag over env var over config file (matching the rest of the config schema).
Why deferred
Policy-config addition; needs a spec on precedence between the CLI flag and config, and product agreement on the default (off, to preserve current behavior on upgrade).
Deferred from the v0.9.3 pre-release review.
Current behavior
--force-tierworks in every mode includinggate. Nothing prevents an author from shippingaltimate review --force-tier=trivial --mode gatein a production GitHub Actions workflow, effectively bypassing the classifier's gate. The bypass is visible in the signed envelope and in the PR-comment headline, but is not blocked.Gap
Administrators enforcing SOX/SOC2 change management have no mechanism to disable the escape hatch on the production path. The flag is marked
[EXPERIMENTAL / bench debug]in--help, but that is advisory text, not enforcement.Proposal
Add a
.altimate/review.ymloption (name TBD, e.g.disableForceTierInGate: true) that causes--force-tierto error out with a non-zero exit when combined with--mode gate. Local and bench runs are unaffected. Config option precedence: CLI flag over env var over config file (matching the rest of the config schema).Why deferred
Policy-config addition; needs a spec on precedence between the CLI flag and config, and product agreement on the default (off, to preserve current behavior on upgrade).