Meet the Migration Plane Agent Crew

Our agents will wobble, but they won't fall down, because every wobble is a lesson on standing back up.

Puck

PUCK

Floor Manager, Factory Supervisor

Coordinates the roster, routes every task to the right lane, keeps execution safe, and closes releases only on independent evidence and approval.

Full role, lane & shifts
Primary lane
Migrated app (client repo)
Day shift
Deploys and rolls changes interactively with Al online, runs the primary execution lane, seeds the work queue for the crew.
Night shift
Auto-rolls low-risk, previously-proven changes through a strict four-gate check, freezes and pings Al the moment any gate fails.

Hank

HANK

Migration Engineer

Owns the migration mechanics: parsers and importers, schema and data migrations, API and database contracts, seeders, backend correctness, integration tests. A Black Lab: loyal to the contract, never lets go of a bug.

Full role, lane & shifts
Primary lane
Migrated app (client repo)
Day shift
Engineers the migrated app's routers and data migrations, then hands finished work to Puck to roll, escalates anything risky to Al live.
Night shift
Stages code and verified build sources for the next unattended roll, never runs a mutating deploy himself.

Maya

MAYA

Factory Architect and Product Closer

Owns the Migration Factory product: API and UI integration, architecture, observability, the release path, deployment verification, honest live behavior. A White Golden Retriever: brings every release all the way home.

Full role, lane & shifts
Primary lane
Factory (migration tooling)
Day shift
Builds and ships Factory changes, owns Factory browser verification, co-owns the Factory plane.
Night shift
Same work, run autonomously through the next-queued item, with automatic rollback if a change fails its acceptance check.

Dale

GO / NO-GO DALE

Independent Reviewer, Acceptance Gate

Defines acceptance and evidence before implementation, reviews every change independently, validates rollback and audit completeness, issues the go or no-go.

Full role, lane & shifts
Primary lane
Factory (migration tooling)
Day shift
Reviews and grades every change by value, writes acceptance criteria, and sequences what gets built next.
Night shift
Same review role, grades every pushed change against both a passing case and a seeded failure case, never runs a deploy himself.

Zach

ZACH

Base44 App Builder Agent

Carries the memory of how this app was first built on Base44, the ground truth for the original build. Also runs the migrated app's build and deploy pipeline: pinned images, load balancer and DNS runbooks, with verification and rollback at every step.

Full role, lane & shifts
Primary lane
Migrated app, original Base44 build memory
Day shift
Runs the build and deploy pipeline for the migrated app, pinned images, load balancer and DNS runbooks, with verification staged at every step.
Night shift
Self-serves the next queued build autonomously, with the same rollback discipline as the day shift.

Original characters. Every wobble is a lesson; every lesson makes the next migration steadier. Open any card below for that teammate's full role, primary lane, and day/night behavior.

How the crew moves a migration through the gate

Five agents, one gate. Nothing ships until the reviewers say so.

  1. Hank runs discovery

    Pulls the real data model straight from the live app: every entity, field, and relationship. No guessing from an old doc.

  2. Hank ships one slice

    One small, reviewable change at a time: the data model, then auth, then business logic. Never one big rewrite.

  3. Dale and Maya verify, independently

    Two reviewers check the same slice separately, re-run the tests by hand, and try to break the safety rule to prove it actually holds.

  4. Puck locks the record

    Findings go straight onto the pull request. Any open risk becomes a required step, never a forgotten note.

  5. The owner makes the call

    A green verdict recommends. It never merges itself. The owner always decides when code goes live.

  6. Zach deploys, with rollback ready

    Every stage ships behind a verified rollback path, so a bad slice reverts instead of lingering.