Behaviour flows

# Behaviour flows

Behaviour maps are maintained as single-purpose diagram leaves, not embedded in this knowledge branch.
Follow the route that matches the question:

- **How does someone reach the studio?** [Access gate](../../../diagrams/flows/access-gate.md).
- **How does a direction become a maintained constellation?** [Onboarding](../../../diagrams/flows/onboarding.md).
- **How is a Domain created?** [Domain creation](../../../diagrams/flows/domain-creation.md).
- **How do machine maintenance and human judgment meet?** [Human loop](../../../diagrams/flows/human-loop.md).
- **How do Streams, Positions, and Directives change state?** [Stream lifecycle](../../../diagrams/flows/stream-lifecycle.md), [Position lifecycle](../../../diagrams/flows/position-lifecycle.md), and [Directive lifecycle](../../../diagrams/flows/directive-lifecycle.md).
- **How does a constellation organise its portfolio?** [Constellation surface](../../../diagrams/ui/constellation.md).
- **How does an entity's evidence become plausible behaviour?** [Entity behaviour composition](../../architecture/WORLD_ENGINE.md#entity-behaviour-needs-a-composition-model) owns the perception → appraisal → action-field contract. It is a model of an actor, not a product behaviour flow.

Chat and Pilot memory are deliberately not a diagram: Chats remain stored with their Domain or
Constellation rather than becoming a separate class. A Pilot turn carries its persisted `toolTrace`, and
`read-chats` is the shared retrieval path across chat kinds.

Raw Markdown source