Minds
Understand the project-scoped runtime that evolves across requests.
A mind is an account-owned runtime that can evolve from actor-attributed experiences across separate requests.
Each mind:
- belongs to exactly one project;
- is addressed by a public
mind_id; - can serve many actors while keeping their experience isolated;
- has one active version of its application instructions;
- can accept messages while earlier updates finish under eventual consistency.
Use separate minds when products, environments, experiments, or trust boundaries must not influence one another. Actor IDs are not a substitute for that isolation boundary.
Fork a settled mind when a new experiment, room, or workflow should begin from the same state and then evolve independently. Forking creates a new active mind, leaves the source unchanged, and never exposes the source's private contents. If the source still has accepted updates in progress, wait for them to settle before retrying the fork.
The public API deliberately exposes behavior and minimal operation status, not the mind's private contents or implementation.