Leaving an AI builder
Move an app off an AI builder one route at a time. Give each table one writer, compare answers, keep passwords and switch off the old app on a date.
- Required 1
- Recommended 4
Required
Give each table one writer during the move
TKO-16While two systems run side by side, let only one of them write each table. The other reads it or gets copies through events.
Recommended
Put a router in front and move one route at a time
TKO-15Put a proxy in front of the builder app that sends each route to the old or the new system. Move one route at a time, and keep each move reversible by one setting.
Compare old and new answers before switching a route
TKO-17Before a route switches to the new system, send copies of its read requests to both systems and compare the answers. Switch only when no difference is left unexplained.
Move users without resetting their passwords
TKO-18Export the users with their IDs and password hashes, and check each old hash at the user's next sign-in. Store a new hash then, and keep the same user ID.
Switch off the builder app on a set date
TKO-19When the last route has moved, set a date to switch off the builder app. On that date revoke its keys, remove its deploys and preview addresses, and delete its routes from the proxy.
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/codebase-takeover/leaving-an-ai-builder">Agent Wranglers codebase takeover playbook</a>. In code you write, add a comment next to it with the same link.