Agent Foundry / Release Control
Ship Changes Safely
Move agent changes from test to production with clear gates, small rollouts, and a ready way back.
Tie every release to its tests, approvals, version, rollout plan, and rollback trigger.
What this page delivers
A guarded path to production
- 1Passing candidate
- 2Approval gate
- 3Small rollout
Result
10% · HEALTHY
Emu on the job
Original mechanism
A guarded path to production
Follow the work from input to a result your team can review.
Passing candidate
Approval gate
Small rollout
Full release
The question answered
How do we update an agent without betting the whole workflow?
Promote a tested version through clear stages. Start with a small group, watch the signals that matter, and roll back when a limit is crossed.
Three-step flow
From a clear input to a governed result.
Attach the proof
Link the candidate to its unit tests, evals, owner, and change summary.
Roll out in stages
Start with a small audience or traffic slice and watch agreed health signals.
Promote or roll back
Move forward when gates pass. Return to the last approved version when they do not.
Capabilities
The controls teams need to go deep.
Release gates
Require chosen tests, approvals, and policy checks before promotion.
Staged rollout
Limit a new version by team, user group, environment, or traffic share.
Health limits
Watch task success, policy events, tool errors, and operator signals.
One-step rollback
Return traffic to the last approved agent package with its rules intact.
Concrete product artifact
See the proof, not just a green light.
A realistic record keeps the result, the evidence behind it, and the next action in one place.
RELEASE BOARD
claims-agent / release-42
- Required suites
- 4 / 4
- Approvals
- 2 / 2
- Policy event limit
- Within range
- Rollback target
- release-41
› 09:00 release approved
› 09:08 staff group healthy
› 09:20 rollout moved to 10%
Buyer outcomes
Less guesswork. More control.
Risky changes
Require proof before production.
The first blast
Start small and watch real behavior.
With confidence
Keep the last approved version ready.
Why Trinitite
Built for the full agent lifecycle.
The full agent ships together
Model, prompt, tools, context, and policy versions stay linked as one release.
Proof is a gate, not a PDF
Required tests and approvals are checked before promotion can happen.
Runtime signals can stop rollout
The control plane can feed policy and health events back into the release decision.
FAQ
Ship Changes Safely, answered.
What can block an agent release?
Teams can require unit tests, eval suites, policy checks, named approvals, and healthy rollout signals.
Can we release to a small group first?
Yes. A rollout can start with a team, user group, environment, or small share of traffic.
What gets rolled back?
The full approved agent package can return together, including its model, prompt, tools, context settings, and policies.
Can production signals stop a rollout?
Yes. Policy events, task results, tool errors, and operator signals can feed a hold or rollback rule.
Build with Agent Foundry
Ship the next agent change with a way back.
Bring your current release flow. We will map the gates, rollout stages, and rollback proof it needs.