[{"data":1,"prerenderedAt":99},["ShallowReactive",2],{"blog-\u002Fblog\u002Fwhy-control-belongs-on-the-edge":3,"blog-surround-\u002Fblog\u002Fwhy-control-belongs-on-the-edge":92},{"id":4,"title":5,"author":6,"badge":7,"body":8,"date":83,"description":84,"extension":85,"meta":86,"navigation":87,"path":88,"seo":89,"stem":90,"__hash__":91},"blog\u002Fblog\u002Fwhy-control-belongs-on-the-edge.md","Why control belongs on the edge","TameChaos","Platform",{"type":9,"value":10,"toc":76},"minimark",[11,15,23,28,31,34,38,41,44,48,51,73],[12,13,14],"p",{},"Sensor-driven systems fail in the gap between a dashboard and the physical world. A\ncontrol loop that has to round-trip every decision through a remote server inherits\nthat server's latency, its outages, and its idea of \"now\". For real-world systems —\nwhere a late command is a wrong command — that gap is the whole problem.",[12,16,17,18,22],{},"TameChaos closes it by making one choice explicit: ",[19,20,21],"strong",{},"the edge is the authoritative\nruntime."," The cloud is something else entirely, and keeping the two jobs separate is\nwhat lets each do its job well.",[24,25,27],"h2",{"id":26},"the-edge-owns-execution","The edge owns execution",[12,29,30],{},"The edge server owns the hardware, runs the experiments, and executes the control\nloop — in real, simulated, or hybrid mode. It does not wait on the network to act. It\nis authoritative for what runs and when, because it is the only thing close enough to\nthe sensors and actuators to be right about it.",[12,32,33],{},"That means the loop you design runs deterministically and repeatably on the device\nthat owns the process, not on a best-effort connection to a region halfway across the\ncountry.",[24,35,37],{"id":36},"the-cloud-aggregates-it-never-commands","The cloud aggregates — it never commands",[12,39,40],{},"The cloud is the non-authoritative layer. It oversees the fleet, aggregates\nlike-processes across edges, and — in the model-loop phase on the roadmap — helps\nimprove the models that each edge pulls and adopts. What it never does is reach in and\nstart, stop, or mutate a live run. Distribution is publish-and-pull, never command.",[12,42,43],{},"This split is not a limitation; it is the design. The edge stays correct under bad\nnetworks because it never depended on the network to be correct. The cloud stays\nuseful because it is freed from the real-time control path to do the thing it is\nactually good at: learning across many edges at once.",[24,45,47],{"id":46},"design-run-improve","Design → Run → Improve",[12,49,50],{},"The same three steps describe every system you build on TameChaos:",[52,53,54,61,67],"ul",{},[55,56,57,60],"li",{},[19,58,59],{},"Design"," sensor arrays, models, and the experiments that exercise them.",[55,62,63,66],{},[19,64,65],{},"Run"," them on the authoritative edge.",[55,68,69,72],{},[19,70,71],{},"Improve"," the models by aggregating like-processes across your fleet.",[12,74,75],{},"The edge is where one and two happen for real. The cloud is where three compounds.\nThat is the whole shape of the platform — and the reason the control loop lives on the\nedge, not behind a dashboard.",{"title":77,"searchDepth":78,"depth":78,"links":79},"",2,[80,81,82],{"id":26,"depth":78,"text":27},{"id":36,"depth":78,"text":37},{"id":46,"depth":78,"text":47},"2026-06-01","Real-world control loops live where the sensors and actuators are. Here is why TameChaos makes the edge the authoritative runtime — and what the cloud is for instead.","md",{},true,"\u002Fblog\u002Fwhy-control-belongs-on-the-edge",{"title":5,"description":84},"blog\u002Fwhy-control-belongs-on-the-edge","IjlvK_moYxOkywUPz7lhZiO-dEiOAe6SZGHcapJLgfw",[93,98],{"title":94,"path":95,"stem":96,"description":97,"children":-1},"The fleet-learning loop, explained","\u002Fblog\u002Fthe-fleet-learning-loop","blog\u002Fthe-fleet-learning-loop","A fleet of edges should get smarter from its own operation. Here is the four-step loop TameChaos Cloud runs — and an honest account of which steps ship today.",null,1780537672749]