The interface is the doorway.
Mission Control lets people define objectives, inspect progress, provide direction and review outcomes. A conversation can participate in this interface without becoming the only source of truth.
The runtime owns execution state.
A durable project identifier ties the work together. The runtime manages the accepted scope, actor identity and execution state. Tool results and completion evidence must be recorded independently of what a model says.
A healthy connection proves reachability. It does not, on its own, prove that a worker is running, an action succeeded, or a workload is safely contained.
Context is retrieved for the project.
Keep instructions small and stable: identity, responsibilities, authority and how to retrieve the right context. Store project facts, artifacts, project history and lessons as durable, versioned records.
At project start, retrieve a bounded context set with source references. Record which lessons were applied and why. At completion, save the outcome and evidence so the next project can resume from reality.
Compute is an explicit layer.
A node supplies capacity. A cluster coordinates several nodes. Federation crosses cluster boundaries and therefore introduces additional ownership, placement and policy decisions.