# Delivery Planning — Team Allocation

> Which team/mob owns which Bolt. A **mob** is a small team owning a Bolt's
> delivery. Per affirmed team practice, this is a solo local project.

## Allocation

This project is a solo local tool (classic scope — the team-formation stage was
skipped). **All Bolts are executed by the single developer agent**
(`aidlc-developer-agent`), in this session, with you approving as each Bolt
completes.

| Bolt | Owner | Notes |
|---|---|---|
| Bolt 1 (`generator` core) | aidlc-developer-agent | build + verify + present |
| Bolt 2a (`ai-draft`) | aidlc-developer-agent | build + verify + present |
| Bolt 2b (`funnies`) | aidlc-developer-agent | build + verify + present |
| Bolt 3 (integration) | aidlc-developer-agent | build + verify + present |

## Program Board note

Single-team (a solo developer), so there is no Program Board — no
cross-team sequencing or hand-off coordination is required. The Bolt plan's
parallelism (2a/2b) is scheduling, not separate teams.

## Approval rhythm

One approval per Bolt, one at a time as they complete (per Q4=A's "reviewed as we
go" for the core, with 2a/2b built in parallel and each reviewed on return).