Edge and cloud

TameChaos splits responsibility along one line: the edge is authoritative for execution, the cloud is authoritative for definitions and identity. Getting this boundary right is what keeps real-world control correct under bad networks while still letting a fleet learn.

The edge is authoritative for execution

The edge server decides which definitions it adopts and runs, and it owns the live runs themselves. It executes the control loop locally, without waiting on the network. Nothing in the cloud can start, stop, or mutate a run — the edge holds that authority because it is the only place close enough to the process to be right about it.

The cloud is authoritative for definitions

The cloud owns template and model definitions and their identity — the registry. It issues template identity, and it observes, aggregates, compares, and suggests. A template is an inert definition until an edge instantiates a run from it.

Publish-and-pull, never command

Because the edge is authoritative for adoption, improved templates and models are published to the fleet and pulled by edges that choose to adopt them. The cloud never pushes a change into a running system. This is the safe direction for real-world control: the device that owns the process decides what it runs.

Model improvement and distribution are the model-loop phase, on the roadmap; fleet oversight and like-process aggregation are the v1 cloud surface today. The authority boundary above holds in both phases — the cloud's role grows, but it never crosses into commanding the edge.