Behaviour flows

From the Meridians Wiki · Public · Maintained · joint

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.
How does a direction become a maintained constellation? Onboarding.
How is a Domain created? Domain creation.
How do machine maintenance and human judgment meet? Human loop.
How do Streams, Positions, and Directives change state? Stream lifecycle, Position lifecycle, and Directive lifecycle.
How does a constellation organise its portfolio? Constellation surface.
How does an entity's evidence become plausible behaviour? Entity behaviour composition 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.