# Concepts

The documentation uses a small set of terms with specific meanings. Each term below is defined before the terms that depend on it, so this page reads best from top to bottom.

## 01 · Body

A body is the set of owned, persistent parts a business needs to exist and transact: a legal entity, a bank account, a card, payments, mail, a site, a database, and an approval queue. Each part exposes an interface that software can call, and each part keeps its state when the model operating the business is replaced. The body holds the credentials for its own accounts, so the accounts belong to the business rather than to any particular model or vendor.

## 02 · Mind

The mind is the model that operates the body. It reads the body's records, decides what to do next, and acts by calling the body's interfaces. The mind holds no state of its own: memory, obligations, and reputation live in the body, and when a better or cheaper model becomes available the owner attaches it to the same body and the business continues. A body with a replaced mind is the same business, in the same way that a company with a new employee is the same company.

## 03 · Limb

A limb is one part of the body seen as a single capability. The bank account is a limb, and so are the card, the mail, the site, and the phone. Some limbs act on the world, and some limbs constrain the body: a spending limit on the card is a limb in the same sense that the card is, because both shape what the business can do.

## 04 · Spawn

Spawning is the operation that provisions a new body. One call registers the entity, opens the bank account, issues the card, connects payments and mail, deploys the site, creates the database and the approval queue, and attaches a mind. The spawn call has its own [reference page](https://busibody.ai/docs/spawn.md), and that page is labeled a draft: today each part is provisioned individually against its provider, and the composed one-call form is being built.

## 05 · Approval queue

The approval queue is where the agent asks its human owner for a decision. When the agent wants to take an action that requires a person, such as sending mail to a stranger or spending above a limit, the request parks in the queue as durable state, and the body resumes that work when the owner answers. Approval starts at approve-each, where the owner approves every action in a category one at a time. A category graduates to approving actions in batches, and then to standing rules, as the record accumulates evidence that the agent handles the category well. The graduations themselves are recorded as events, so the history of what the agent was trusted with, and when, can be read back later.

## 06 · Event

An event is one typed, timestamped record of a fact about the business: a lead was captured, a message was approved, a payment arrived. Events are appended to a log and never edited or deleted, and every table the business uses, such as its list of leads or its revenue, is a view computed from the event log. The event schema has its own [reference page](https://busibody.ai/docs/events.md), and the schema on that page is the one the first body runs today.