[{"data":1,"prerenderedAt":181},["ShallowReactive",2],{"blog-\u002Fblog\u002Fwhy-studio-leads":3,"blog-surround-\u002Fblog\u002Fwhy-studio-leads":174},{"id":4,"title":5,"author":6,"badge":7,"body":8,"date":165,"description":166,"extension":167,"meta":168,"navigation":169,"path":170,"seo":171,"stem":172,"__hash__":173},"blog\u002Fblog\u002Fwhy-studio-leads.md","Why the design tool moved to the front","TameChaos","Direction",{"type":9,"value":10,"toc":156},"minimark",[11,20,23,28,34,50,58,62,65,72,79,86,90,97,104,107,111,118,125,129,132],[12,13,14,15,19],"p",{},"Until recently this site opened with the edge: the authoritative runtime, the thing that\nowns your hardware and executes your experiments where the sensors are. That is still what\nthe edge is, and it is still the part of the platform we would defend hardest. But it is no\nlonger the first thing we put in front of you. ",[16,17,18],"strong",{},"TameChaos Studio leads now"," — the design\nsystem where a real-world system gets modeled, specified, and documented before any of it is\nbuilt.",[12,21,22],{},"Reordering a product line-up in public invites one obvious reading — that the thing which\nmoved down is being quietly abandoned. That reading is wrong here, and it is worth spending\na post on why.",[24,25,27],"h2",{"id":26},"what-changed-is-the-order-not-the-architecture","What changed is the order, not the architecture",[12,29,30,31],{},"The four products are the same four: Studio designs, Field takes that design into the field\non Android, the edge executes, and the cloud aggregates across the edges you own. What\nchanged is which one we lead with, and one architectural statement that had been implicit\nand is now explicit: ",[16,32,33],{},"authority divides by role, not by product.",[35,36,37,44],"ul",{},[38,39,40,43],"li",{},[16,41,42],{},"Studio holds design-time authority"," — the systems model, the type vocabulary, the\nsymbols bound to it, the catalog selections, and the bill of materials projected from them.",[38,45,46,49],{},[16,47,48],{},"The runtime engine holds authority over execution"," — physics, simulation, measured\nreality, results. That role is realized today by the edge server.",[12,51,52,53,57],{},"Writing that down is what made leading with a design tool coherent instead of contradictory.\n\"The edge is the authoritative runtime\" now reads precisely: the ",[54,55,56],"em",{},"runtime engine"," is\nauthoritative over execution, wherever it is hosted, and the edge is that engine's first and\ncurrent host. Nothing about execution moved into Studio.",[24,59,61],{"id":60},"why-the-design-tool-goes-first","Why the design tool goes first",[12,63,64],{},"Two reasons, one about our users and one about us.",[12,66,67,68,71],{},"The first: ",[16,69,70],{},"most of the work starts at design, and design is where a tool can be useful\nwith zero hardware present."," You can model a facility, lay out the process and control\ntopology, draw it with symbols an instrumentation engineer recognises, mock up the operator\nviews, and export an engineering package — with no server, no network, and nothing bought.\nA runtime cannot be useful that early, because there is nothing yet to run.",[12,73,74,75,78],{},"The second: ",[16,76,77],{},"specifying a design against real parts is where the money is."," Once a placed\nnode on a drawing carries the actual part it stands for, the bill of materials stops being a\nspreadsheet somebody maintains beside the drawing and becomes something the drawing produces\n— with quantities, the accessories and licences a part implies, and the gaps you have not\nspecified yet named as gaps. That is the sharpest near-term value we can build, and it lives\nentirely on the design side.",[12,80,81,82,85],{},"We should be equally clear about what that means today: Studio is pre-release, with the\nfirst release targeted for ",[16,83,84],{},"August 31, 2026",", and the node-first bill of materials is part\nof that first release rather than something you can use now. The catalog underneath it is a\nmodel and a taxonomy, not a populated database — so you will not find part counts or\ncoverage claims anywhere on this site.",[24,87,89],{"id":88},"why-this-is-not-a-retreat-from-the-edge","Why this is not a retreat from the edge",[12,91,92,93,96],{},"Because the edge was reprioritized ",[16,94,95],{},"in sequence, not in importance"," — and because the\nsplit above is not symmetric.",[12,98,99,100,103],{},"A design is a claim about what a system will do. A run is a measurement of what it actually\ndid. ",[16,101,102],{},"A design never overrules measured reality."," We considered giving Studio stronger\nauthority over a runtime and rejected it outright: the whole value of an authoritative\nruntime is that the thing closest to the process gets to be right about the process. Studio\nowns the model; the runtime owns the result.",[12,105,106],{},"Everything that made the edge worth building is intact. Runs execute locally, without waiting\non a network. The edge decides which templates and models it adopts. The cloud observes,\naggregates, compares, and suggests, and it never starts, stops, or mutates a run —\ndistribution is publish-and-pull, in that direction, always. Aggregation stays scoped to the\nedges you own; there is no cross-tenant sharing.",[24,108,110],{"id":109},"the-seam-is-a-package-not-a-pipe","The seam is a package, not a pipe",[12,112,113,114,117],{},"The place where the two authorities meet is a ",[16,115,116],{},"self-describing project package",". A project\ncarries its own vocabulary — the base it started from plus whatever the project adds — so a\nruntime can learn the kinds inside a design from the package rather than from a schema both\nsides had to compile in advance.",[12,119,120,121,124],{},"That is a better boundary than a live connection between two applications, for a reason that\nhas nothing to do with product order: it lets the vocabulary be yours to extend, and it does\nnot care which engine eventually reads the package. It is also the honest state of things.\nThe design → runtime export is committed ",[16,122,123],{},"as a design, not as a working path"," — Studio can\nwrite a structured package, but that package has not yet been validated against a live edge\ningest contract, and pushing a project straight to an edge server sits outside the first\nStudio release. Today the seam is a package you carry, not a button that deploys.",[24,126,128],{"id":127},"where-this-leaves-you","Where this leaves you",[12,130,131],{},"The four products are peers, not a funnel. If you only ever model systems and hand documented\npackages to whoever builds them, Studio on its own is a complete answer and we are not going\nto pretend otherwise to sell you a runtime. If you run experiments against real hardware,\nthe edge is exactly where it was — first in importance, third in the line-up, and unmoved in\nwhat it owns.",[12,133,134,135,140,141,145,146,150,151,155],{},"The ",[136,137,139],"a",{"href":138},"\u002Fdocs","docs"," carry the whole split in more detail: ",[136,142,144],{"href":143},"\u002Fdocs\u002Fstudio","Studio"," for the design\nside, ",[136,147,149],{"href":148},"\u002Fdocs\u002Fedge-and-cloud","Edge and cloud"," for the runtime and aggregation halves, and\n",[136,152,154],{"href":153},"\u002Fdocs\u002Fcore-concepts","Core concepts"," for the vocabulary on both sides of the boundary.",{"title":157,"searchDepth":158,"depth":158,"links":159},"",2,[160,161,162,163,164],{"id":26,"depth":158,"text":27},{"id":60,"depth":158,"text":61},{"id":88,"depth":158,"text":89},{"id":109,"depth":158,"text":110},{"id":127,"depth":158,"text":128},"2026-07-29","TameChaos now leads with Studio rather than the edge runtime. Here is the reasoning — and why reordering the products is not a retreat from the edge.","md",{},true,"\u002Fblog\u002Fwhy-studio-leads",{"title":5,"description":166},"blog\u002Fwhy-studio-leads","9jU6Cly33G0X4dzKNXABfXXfBBYKM1nLSZRu60trn9E",[175,180],{"title":176,"path":177,"stem":178,"description":179,"children":-1},"Why control belongs on the edge","\u002Fblog\u002Fwhy-control-belongs-on-the-edge","blog\u002Fwhy-control-belongs-on-the-edge","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.",null,1785465247511]