Backend maintenance
Functional acceptance within policy; no observed increase in review revisions
−38%
Move to canary
Example Stack Release Evaluation
Stack Release Evaluation
A one-page release decision showing which workloads can move to a candidate, which should stay on the current stack, and where the evidence is still insufficient. This example uses cost migration as the trigger.
The cost denominator is an accepted-task equivalent after a frozen repetition-aggregation policy. This example does not claim causation or that any named vendor or model performs as shown.
Current
Claude Code · Opus · backend-tools@17
Candidate
Candidate harness · alternate model route · backend-tools@18
Frozen policy
Accepted task · required verification · review intervention · regressions
€8.10 current
€5.02 candidate
−38% change
Test repair
Equivalent required verification; reviewer intervention unchanged
−36%
Move to canary
Database migrations
Three candidate-only regressions in private qualification
−31%
Keep baseline
Authentication
Insufficient comparable evidence under the frozen policy
Unavailable
Continue evaluation
Projected safe annualized saving
Unavailable
A projection requires customer-supplied baseline spend, eligible workload volume, verified cost coverage, and an agreed attribution window. Fullbeam does not invent it.
Example rollout decision
- Move to controlled production exposure
- Backend maintenance · Test repair
- Keep the current stack
- Database migrations
- Continue qualification
- Authentication
Review verifies the output. Qualification governs the producer.
Your review layer still decides whether each pull request is acceptable. Fullbeam always uses private qualification to decide whether the candidate stack should receive more work; where Stack-level runtime identity is supported, controlled production evidence can confirm the decision.