[{"data":1,"prerenderedAt":163},["ShallowReactive",2],{"docs-\u002Fdocs\u002Fedge-and-cloud":3,"docs-navigation":143,"docs-surround-\u002Fdocs\u002Fedge-and-cloud":159},{"id":4,"title":5,"body":6,"description":134,"extension":135,"meta":136,"navigation":137,"path":138,"seo":139,"stem":140,"updated":141,"__hash__":142},"docs\u002Fdocs\u002F3.edge-and-cloud.md","Edge and cloud",{"type":7,"value":8,"toc":127},"minimark",[9,22,27,30,34,41,105,109,120],[10,11,12,13,17,18,21],"p",{},"TameChaos splits responsibility along one line: the edge is authoritative for\n",[14,15,16],"strong",{},"execution",", the cloud is authoritative for ",[14,19,20],{},"definitions and identity",". Getting this\nboundary right is what keeps real-world control correct under bad networks while still\nletting a fleet learn.",[23,24,26],"h2",{"id":25},"the-edge-is-authoritative-for-execution","The edge is authoritative for execution",[10,28,29],{},"The edge server decides which definitions it adopts and runs, and it owns the live runs\nthemselves. It executes the control loop locally, without waiting on the network. Nothing\nin the cloud can start, stop, or mutate a run — the edge holds that authority because it\nis the only place close enough to the process to be right about it.",[23,31,33],{"id":32},"the-cloud-is-authoritative-for-definitions","The cloud is authoritative for definitions",[10,35,36,37,40],{},"The cloud owns template and model ",[14,38,39],{},"definitions"," and their identity — the registry. It\nissues template identity, and it observes, aggregates, compares, and suggests. A template\nis an inert definition until an edge instantiates a run from it.",[42,43,44,60],"table",{},[45,46,47],"thead",{},[48,49,50,54,57],"tr",{},[51,52,53],"th",{},"Concern",[51,55,56],{},"Edge",[51,58,59],{},"Cloud",[61,62,63,75,85,95],"tbody",{},[48,64,65,69,72],{},[66,67,68],"td",{},"Live runs (start\u002Fstop\u002Fmutate)",[66,70,71],{},"Authoritative",[66,73,74],{},"Never",[48,76,77,80,82],{},[66,78,79],{},"Adoption of a template\u002Fmodel",[66,81,71],{},[66,83,84],{},"Suggests",[48,86,87,90,93],{},[66,88,89],{},"Template & model definitions",[66,91,92],{},"Pulls & runs",[66,94,71],{},[48,96,97,100,103],{},[66,98,99],{},"Fleet oversight & aggregation",[66,101,102],{},"Reports",[66,104,71],{},[23,106,108],{"id":107},"publish-and-pull-never-command","Publish-and-pull, never command",[10,110,111,112,115,116,119],{},"Because the edge is authoritative for adoption, improved templates and models are\n",[14,113,114],{},"published"," to the fleet and ",[14,117,118],{},"pulled"," by edges that choose to adopt them. The cloud\nnever pushes a change into a running system. This is the safe direction for real-world\ncontrol: the device that owns the process decides what it runs.",[10,121,122,123,126],{},"Model improvement and distribution are the ",[14,124,125],{},"model-loop phase, on the roadmap","; fleet\noversight and like-process aggregation are the v1 cloud surface today. The authority\nboundary above holds in both phases — the cloud's role grows, but it never crosses into\ncommanding the edge.",{"title":128,"searchDepth":129,"depth":129,"links":130},"",2,[131,132,133],{"id":25,"depth":129,"text":26},{"id":32,"depth":129,"text":33},{"id":107,"depth":129,"text":108},"Which responsibilities sit on the authoritative edge and which sit in the non-authoritative cloud — and why distribution is publish-and-pull, never command.","md",{},true,"\u002Fdocs\u002Fedge-and-cloud",{"title":5,"description":134},"docs\u002F3.edge-and-cloud","2026-06-01","oXt630i6i8WLOwMhZvGbP5_ZdYoqKTYJk_uudgyBy6A",[144],{"title":145,"path":146,"stem":147,"children":148,"page":158},"Docs","\u002Fdocs","docs",[149,153,157],{"title":150,"path":151,"stem":152},"Getting started","\u002Fdocs\u002Fgetting-started","docs\u002F1.getting-started",{"title":154,"path":155,"stem":156},"Core concepts","\u002Fdocs\u002Fcore-concepts","docs\u002F2.core-concepts",{"title":5,"path":138,"stem":140},false,[160,162],{"title":154,"path":155,"stem":156,"description":161,"children":-1},"The vocabulary of TameChaos — sensor arrays, experiments, runs, and the process-class templates that make runs comparable across a fleet.",null,1780537673022]