Expertise
Agent-Driven Modernization
Migrations carried by agents, gated by test evidence
Overview
Framework upgrades, dependency migrations, and large mechanical refactors are repetitive, well specified, and dull. That makes them good agent work, provided every change arrives with the test evidence that proves it and a release gate that refuses anything without it.
Positioning
The agent does the migration; the test suite and the release gate decide whether it lands. The person's job moves from doing the change to designing the gate.
What this means in practice
Break the migration into phases with explicit file ownership so parallel agents never collide, give each phase its red-first tests, require the agent to show the failing run and the passing run, and let a release gate fail on any phase without both.
Why this matters
We run our own Flutter and Astro products this way; a release pipeline with 1,780 tests gates one of them. The same discipline transfers to Angular, React, and Nx platforms.
What we deliver
A phased plan that says which agent owns which files
Red-first tests per phase
A release gate that fails on missing evidence
Knowledge paths
Related insights
Insight / Agent-Driven Modernization
Rebuilding this site with agents, in phases that cannot collide
The repositioning you are reading was carried out by cheaper agents working in parallel worktrees under a file-ownership manifest, with a failing test shown before every change. What the audit found first, how the phases were cut, and what the record shows.