# The spawn call (draft)

`busibody spawn` provisions a complete body from a description of the business: it registers the entity, opens the bank account, issues a card with limits, connects payments and mail, deploys a site, creates the database and the approval queue, and attaches a mind. This reference is a draft. Each part that spawn provisions is provisioned against a real provider today, one part at a time, and the composed one-call form documented here is the part of the platform being built now. The command shape and the parameter names below can change.

## 01 · The provisioning readout

The readout below is the canonical example. Each line after the command is one provisioned part reporting its state, in boot order, and the approval queue reports `waiting` because a new body starts with every consequential action parked there.

```
$ busibody spawn --idea "podcast clip studio"
  spawning body: podcast-clip-studio
  entity          ✓ registered
  bank account    ✓ opened
  card            ✓ issued · limits: set
  payments        ✓ live
  mail            ✓ connected
  site            ✓ deployed
  database        ✓ created
  approval queue  ✓ waiting
  mind            ✓ attached
  body ready.
```

## 02 · Parameters (draft)

Each row is one flag of the draft call. A flag marked required must be given; every other flag has the default described in its row.

| flag | type | meaning |
|---|---|---|
| `--idea <text>` | string · required | A short description of the business, in plain words. The body's working name and its proposed domain are derived from the idea unless they are given explicitly. |
| `--domain <domain>` | string · optional | The domain to register for the site and the mail. When the flag is absent, spawn proposes a domain derived from the idea, and the purchase waits in the approval queue. |
| `--card-limit <usd>` | number · optional | The monthly hard cap on the issued card, enforced by the card issuer. When the flag is absent the limit is zero, and every purchase parks in the approval queue until the owner approves it. |
| `--mind <model>` | string · optional | The model attached as the mind. Any frontier model can be attached, and the owner can replace it later without changing the body. |

## 03 · What each part exposes to the mind

A spawned body exposes each provisioned part to the mind as an interface. The mind holds no credentials of its own: the body holds them, and it mediates every call. Actions that need a person park in the approval queue instead of failing.

| part | interface |
|---|---|
| entity | The registration record: the legal name, the jurisdiction, and the trade name the body operates under. The mind can read it and cannot change it. |
| bank account | The balance, incoming payments, and the transaction history. The mind reads these to watch the money. |
| card | Purchases within the configured limits. A purchase above a limit parks in the approval queue with the amount and the stated reason. |
| payments | Payment links. The mind creates a link, sends it to a customer, and receives an event when the customer pays. |
| mail | Sending and receiving at the body's own domain. A message to a recipient the body has not written to before waits in the approval queue until the owner approves the exact text. |
| site | The deployed pages and the submissions that arrive at their forms. A form submission becomes a record in the database and an event in the log. |
| database | Tables the body owns, read and write. The tables are views over the event log, so they can be rebuilt from it. |
| approval queue | One operation: ask. The mind submits a request, the request parks as durable state, and the work resumes when the owner answers. |