Expand description
ChangeOps release gating engine: evaluates diffs, coverage, and eval signals to decide whether a change may ship automatically, requires follow-up, or must be blocked. Designed to be deterministic so gating decisions can be replayed and exported as artifacts.
Structs§
- Budget
Signal - Budget or cost signal derived from the change (e.g. projected spend).
- Budget
Summary - Change
Diff - Summary of a single diff considered by the gate.
- Change
Followup Record - Recorded follow-up decision.
- Change
Followup Request - Change follow-up request (manual acknowledgement).
- Change
Gate Decision - Final decision payload from the ChangeOps gate.
- Change
Gate Engine - Change
Gate Request - Inputs considered by the gating engine.
- Coverage
Component - Aggregated coverage information per component or file group.
- Coverage
Report - Coverage report derived from telemetry or test runs.
- Coverage
Summary - Decision
Scorecard - Scorecard summarising the inputs considered while evaluating the gate.
- Eval
Metric - Evaluation metric emitted by change validation (eval packs, smoke tests, etc.).
- Eval
Summary - Followup
Action - Suggested follow-up action when the gate cannot auto-approve.
- Novelty
Summary - Thresholds
Enums§
- Change
Decision Effect - Primary effect returned by the gating engine.
- Change
Gate Error - Errors produced while evaluating the gate.
- Followup
Outcome - Metric
Direction - Direction for metric thresholds.