# Release-change record

Hypothetical teaching comparison, not permission to release software. No trained-model result, representative workload, live canary, operator-capacity measurement, or customer outcome is established.

## Completed comparison

- Purpose: compare a proposed coordinator-review rule on identical declared cases.
- Current: teaching-routing@1, score at least 0.80 AND value at least USD 10,000.
- Candidate: teaching-routing@2-candidate, score at least 0.70 AND the same value condition.
- Shared: supplied customer and read-permission checks, evidence flag, valid score, USD 0.20 cost cap, and permission to prepare a review. These are local code branches, not production enforcement.
- Inputs: eight authored records; scores, freshness flags, costs, and permissions are declared, not measured.
- Changed cases: score 0.75/value USD 15,000 and score 0.72/value USD 11,000 change from no action to review.
- First changed trace step: route_selected for both. Earlier declared checks agree.
- Unchanged cases: score 0.82 remains review; score 0.60 and low value remain no action; stale evidence and cost USD 0.21 remain escalated; wrong tenant remains denied.
- Review count: 1 current, 3 candidate across this exact pack.
- Declared planning assumption: six minutes per review and twelve available minutes for the pack. Demand is 6 versus 18 minutes. Candidate exceeds this authored capacity by 6 minutes.
- Missing evidence: checked real-system answers, why the cases represent the work, actual review quality and available time, full cost, current permissions, exact code and settings, compatibility, rollout and recovery tests, and operating-owner acceptance.
- Current disposition: hold. No real approval exists. Workflow and service owners would need to resolve capacity and target evidence before seeking release approval.
- Recovery limit: restoring a rule does not remove reviews already prepared. Keep their saved records and operation IDs, with someone responsible for checking unresolved results.

Changing the rule used to grade an unchanged saved answer may allow that answer to be graded again, if everything needed for the new check was retained. Changing the shipment-routing threshold can change execution, so rerun the affected steps. Keep the original results with the versions that produced them.

## Your comparison

| Field                            | Record for permitted work                                                                                               |
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Change and accountable owner     | Reason, scope, intended improvement                                                                                     |
| Current and candidate revisions  | Exact versions of the code, settings, policy, prepared context, tools, model, and checker that apply                    |
| Input evidence                   | Source versions, cases, period, permissions, and excluded or unresolved work                                            |
| Tests agreed before comparison   | Expected changes, safety cases that must not change, separately checked answers, and cases kept out of development      |
| Old and new result for each case | Decision under each version, first observed difference, failures, and uncertainty                                       |
| Consequences for later work      | Review demand, accepted results, costs, delays, and possible errors                                                     |
| Evidence of available team time  | Measured arrivals and review durations, busy periods, qualified cover, and safe response to overflow                    |
| Proposed rollout limits          | Which cases, how long, what monitoring, and which owner; not an approval                                                |
| Stop and recovery                | Alert, reason to stop new work or disable the service, previous compatible version, and checking work already submitted |
| Decision                         | Hold / repair and retest / seek scoped approval / abandon; who may decide and supporting evidence                       |

Keep primary records permitted and protected. Do not paste private customer data, secrets, or restricted source locations into a public worksheet.