AI Workforce · Module
Agent Replacement
Swap an agent version or template without losing your context
Agent Replacement swaps an underperforming agent version or template while keeping the tenant's context, comparing both in shadow before cutover. In Year 1, replacement is a manual process run by One3 support.
Replacing without starting over
When an agent underperforms, replacing it usually means losing everything it learned about your business. Agent Replacement, planned for W3, is designed to carry that context across. In Year 1, replacement is handled manually by One3 support.
Why a replacement starts
A replacement request can come from the owner, from a monthly review recommendation or from a template's kill criteria.
The ContextBundle
A ContextBundle collects what matters about the tenant: memory items, playbook overrides, approved examples, KPI baselines, guardrails, persona choice and connections. A compatibility report checks that the new version's skill and memory schemas accept the bundle, and mismatches go to human review.
Shadow, compare, cut over
In dual shadow, both versions run on the same live inputs and are compared on agreement, quality, cost and safety. Cutover has a rollback window, and in-flight runs are drained or handed over. One ledger account lineage continues across versions, and statements show the split, so ROI history is not lost.
Fair terms
There is no new setup fee for same-family replacements. Bulk replacement across a tenant's instances of a template major version starts with an opt-in canary. Cross-family replacement to a different template needs re-probation for the new skills. The old instance is offboarded with identity revoked and memory archived or erased per retention.
How it fits
Replacement draws on the rental contract in the Agent Rental Marketplace, the agent versions in Agents Studio and the Investment & ROI Ledger. A monthly review that recommends "replace" can start the process directly, and template kill criteria in the Store can trigger bulk replacement when a template version is retired. The tenant always decides when to cut over, and can roll back inside the window.
Features
What Agent Replacement includes
Replacement requests
From the owner, a monthly review or template kill criteria.
ContextBundle
Memory, playbook overrides, examples, baselines, guardrails, persona and connections.
Compatibility report
Schema checks with mismatches sent to human review.
Dual shadow comparison
Agreement, quality, cost and safety on the same live inputs.
Cutover with rollback
In-flight runs drained or handed over.
Ledger lineage
One account lineage across versions with the split shown.
No setup fee for same-family swaps
Contract rule.
Bulk replacement
Across instances with an opt-in canary.
Cross-family replacement
Re-probation for new skills.
Old instance offboarding
Identity revoked; memory archived or erased.
Workflow
Replace an agent
- 1
Raise a replacement request
- 2
Assemble the ContextBundle
- 3
Check compatibility
- 4
Run both versions in shadow
- 5
Cut over with a rollback window
- 6
Offboard the old instance
AI
AI skills and Digital Employees
Compatibility checking
Finds bundle mismatches for review.
Shadow comparison summary
Summarises differences between versions.
Frequently asked questions
Do I lose my ROI history?
No. One ledger account lineage continues across versions.
Is there a fee to replace an agent?
No new setup fee for same-family replacements.
What happens in Year 1?
Replacement is a manual process run by One3 support. The engine is planned for W3.
See Agent Replacement in your workflow
Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.