[{"data":1,"prerenderedAt":409},["ShallowReactive",2],{"docs-\u002Fdocs\u002Fstudio":3,"docs-navigation":387,"docs-surround-\u002Fdocs\u002Fstudio":404},{"id":4,"title":5,"body":6,"description":378,"extension":379,"meta":380,"navigation":381,"path":382,"seo":383,"stem":384,"updated":385,"__hash__":386},"docs\u002Fdocs\u002F3.studio.md","Studio",{"type":7,"value":8,"toc":367},"minimark",[9,17,24,29,32,92,99,103,143,147,154,157,171,180,184,199,218,229,233,236,326,329,333,350,354],[10,11,12,16],"p",{},[13,14,15],"strong",{},"TameChaos Studio"," is the experimental design system: model a real-world system, specify\nit against real parts, and take a documented, procurable package out the other end. It is\nwhere most work starts, and it is standalone — Studio delivers its whole output with no\nruntime, no server, and no network.",[10,18,19,20,23],{},"Studio is pre-release. The first release is targeted for ",[13,21,22],{},"August 31, 2026",", and this page\nmarks anything that arrives with that release rather than describing it as though it already\nshipped.",[25,26,28],"h2",{"id":27},"the-platforms","The platforms",[10,30,31],{},"Studio is several implementations of one design core over one project format:",[33,34,35,48],"table",{},[36,37,38],"thead",{},[39,40,41,45],"tr",{},[42,43,44],"th",{},"Platform",[42,46,47],{},"What it is",[49,50,51,62,72,82],"tbody",{},[39,52,53,59],{},[54,55,56],"td",{},[13,57,58],{},"Mac",[54,60,61],{},"The primary engineering workstation — full canvas authoring, sourcing, and the documentation export",[39,63,64,69],{},[54,65,66],{},[13,67,68],{},"iPad",[54,70,71],{},"A touch-first authoring surface, not a viewer — topology, HMI mockups, facilities, sourcing",[39,73,74,79],{},[54,75,76],{},[13,77,78],{},"iPhone",[54,80,81],{},"The same project navigator in compact form: everything but the canvas, including node-first capture straight into the physical-process diagram",[39,83,84,89],{},[54,85,86],{},[13,87,88],{},"Windows",[54,90,91],{},"A WPF application on .NET 10, a close sibling of the Mac app on the same design core — in the first release alongside it",[10,93,94,95,98],{},"Android is ",[13,96,97],{},"TameChaos Field",": the Android platform surface of this same core, and its own\nproduct rather than a fifth Studio build, because it adds an optional Edge companion and\nrugged hardware the other platforms cannot offer.",[25,100,102],{"id":101},"what-you-model","What you model",[104,105,106,113,119,125,131,137],"ul",{},[107,108,109,112],"li",{},[13,110,111],{},"Facilities"," — a project holds one or more facilities, and every diagram belongs to\nexactly one of them. A facility owns both the physical process and the comms-and-control\nside of a place, and carries a real-world location.",[107,114,115,118],{},[13,116,117],{},"Physical process topology"," — vessels, pumps, valves, sensor mounts; the connections\nbetween them designated as pipe, wire, conduit, or rail; and panels and cabinets that own\nwhat you drop inside them.",[107,120,121,124],{},[13,122,123],{},"Communication and control topology"," — PLCs, RTUs, HMIs, historians, and gateways with\nprotocol, segment, and vendor metadata. Drafting only: Studio does not simulate the\ntransport.",[107,126,127,130],{},[13,128,129],{},"Operator views"," — HMI and dashboard mockups bound to your sensors with units and\nthresholds. Design artifacts, not live dashboards.",[107,132,133,136],{},[13,134,135],{},"The engineering notebook"," — markdown notes attached to the project or to any node,\nsearchable across the project.",[107,138,139,142],{},[13,140,141],{},"The documentation package"," — topology, comms, sourcing, mockups, and notes exported as\nMarkdown and PDF. This is the standalone deliverable.",[25,144,146],{"id":145},"design-authority","Design authority",[10,148,149,150,153],{},"Studio is the ",[13,151,152],{},"design-time authority"," for the systems model: the topology, the facility,\nthe type vocabulary, the symbols bound to it, the catalog selections, and the bill of\nmaterials projected from them. Nothing upstream caps what you are allowed to model — the\nvocabulary is Studio's to author, not something a runtime hands down.",[10,155,156],{},"Two consequences worth understanding:",[104,158,159,165],{},[107,160,161,164],{},[13,162,163],{},"Projects describe themselves."," In the first release a Studio project carries its own\nvocabulary — the base version it started from, plus whatever the project adds and the\nsymbol bound to each kind — so it opens and validates on its own terms rather than against\na schema compiled into another application.",[107,166,167,170],{},[13,168,169],{},"Defining your own kinds is on the roadmap."," Adding component kinds the base vocabulary\ndoes not have, binding each one a symbol, and curating a palette down to your discipline\nis decided, and lands after the first release.",[10,172,173,174,179],{},"Design authority does not mean authority over a running system. Studio owns the design; the\nruntime owns the result; a design never overrules what a running system measures. The two\nmeet at that self-describing project package — a package a runtime reads and validates, not\na live pipe into it. ",[175,176,178],"a",{"href":177},"\u002Fdocs\u002Fedge-and-cloud","Edge and cloud"," covers the runtime side of the\nsame boundary.",[25,181,183],{"id":182},"standards-compatible-symbols","Standards-compatible symbols",[10,185,186,187,190,191,194,195,198],{},"Studio draws with a symbol library built to standard-faithful geometry — ",[13,188,189],{},"ANSI\u002FISA-5.1",",\n",[13,192,193],{},"IEC 60617",", and ",[13,196,197],{},"IEC 61131-3"," — redrawn in the TameChaos line style. An ISA field\ninstrument is a bare circle with a loop tag; a gate valve is a bowtie; an IEC 61131 contact\nis two bars on a rung.",[104,200,201,208,215],{},[107,202,203,204,207],{},"Each symbol carries ",[13,205,206],{},"named connection ports"," typed by what they carry — process, signal,\nelectrical, mechanical, data — so an editor can route lines and refuse a connection that\nmakes no sense. ISA loop tags are typeset over the body rather than baked into the artwork.",[107,209,210,211,214],{},"A ",[13,212,213],{},"general-control base"," covers most process and control drawings whatever the sector;\nwater and wastewater, manufacturing, facilities, HVAC air-side, electrical, and PLC logic\nlayer on top of it as thin profiles rather than as duplicate libraries that drift apart.",[107,216,217],{},"The library is drawn and shipped in the TameChaos design system today. Enabling packages\nper project and binding a symbol to each of your component kinds arrives with the first\nStudio release.",[10,219,220,221,224,225,228],{},"Two limits, stated plainly: the symbols are ",[13,222,223],{},"compatible with"," those standards and\nreference them by name — they are ",[13,226,227],{},"not certified"," against them. And standards-faithful\nsymbols do not make Studio a P&ID editor; it remains a design and documentation\nenvironment.",[25,230,232],{"id":231},"where-procurement-fits","Where procurement fits",[10,234,235],{},"Specifying a design against real parts is what makes a number at the end of it possible.\nThe pieces, and how far each one goes today:",[33,237,238,248],{},[36,239,240],{},[39,241,242,245],{},[42,243,244],{},"Capability",[42,246,247],{},"Where it stands",[49,249,250,262,273,283,293,304,315],{},[39,251,252,259],{},[54,253,254,255,258],{},"A placed node carries its own catalog part, so the ",[13,256,257],{},"bill of materials is generated from the drawing"," — quantity per instance, rolled up across instances",[54,260,261],{},"In the first release",[39,263,264,271],{},[54,265,266,267,270],{},"The BOM walks the ",[13,268,269],{},"whole"," drawing: components, connectors as procurable media (pipe by length and diameter, wire by gauge, conduit by trade size), and enclosures as a line item plus their contents",[54,272,261],{},[39,274,275,281],{},[54,276,210,277,280],{},[13,278,279],{},"vendor-neutral catalog"," underneath, classified by a shared taxonomy — which is what lets a line derive the accessories, licences, services, and documentation a part implies, and surface an unspecified node as a gap",[54,282,261],{},[39,284,285,291],{},[54,286,287,290],{},[13,288,289],{},"Budgetary pricing"," stamped with the date it was priced, rendering as stale past a threshold. Never a quote, and it never reorders or favours a vendor",[54,292,261],{},[39,294,295,302],{},[54,296,297,298,301],{},"The ",[13,299,300],{},"Procurement Package"," — the BOM plus the design that produced it, exported as one versioned artifact you can snapshot",[54,303,261],{},[39,305,306,312],{},[54,307,308,311],{},[13,309,310],{},"Supplier offers"," in Sourcing — vendor-identified price breaks, stock, lead time, minimum order",[54,313,314],{},"On the roadmap; not a settled decision yet",[39,316,317,323],{},[54,318,210,319,322],{},[13,320,321],{},"private RFQ"," — publish an immutable snapshot to specific vetted integrators you invite, and receive sealed bids only you can see",[54,324,325],{},"On the roadmap",[10,327,328],{},"Studio plans; it does not buy. There is no live distributor feed, no ordering rail, and no\nquote or purchase-order generation anywhere in it. A private RFQ is directed and never\nopenly listed: no directory to browse, no live ranking, no integrator seeing who else you\nasked — and TameChaos brokers that exchange without being a party to it.",[25,330,332],{"id":331},"what-studio-is-not","What Studio is not",[104,334,335,338,341,344,347],{},[107,336,337],{},"Not a runtime, and not a SCADA or DCS replacement.",[107,339,340],{},"Not a simulation engine, a digital twin, or a live telemetry surface.",[107,342,343],{},"Not a historian.",[107,345,346],{},"Not a P&ID editor, and its standards-compatible symbols are not certified ones.",[107,348,349],{},"Not a purchasing system.",[25,351,353],{"id":352},"where-to-next","Where to next",[104,355,356,362],{},[107,357,358,361],{},[13,359,360],{},"Core concepts"," — the design-side vocabulary in detail: Studio projects, facilities,\ncomponents, connectors, containers, and the bill of materials.",[107,363,364,366],{},[13,365,178],{}," — the runtime half of the authority boundary, and why distribution is\npublish-and-pull.",{"title":368,"searchDepth":369,"depth":369,"links":370},"",2,[371,372,373,374,375,376,377],{"id":27,"depth":369,"text":28},{"id":101,"depth":369,"text":102},{"id":145,"depth":369,"text":146},{"id":182,"depth":369,"text":183},{"id":231,"depth":369,"text":232},{"id":331,"depth":369,"text":332},{"id":352,"depth":369,"text":353},"An orientation to TameChaos Studio, the experimental design system — the platforms it runs on, the design authority it holds, its standards-compatible symbols, and where procurement fits.","md",{},true,"\u002Fdocs\u002Fstudio",{"title":5,"description":378},"docs\u002F3.studio","2026-07-29","9J7QfKqMViN_eegR3EmRj0bd0_G3cwXZ5QjkOpqPorg",[388],{"title":389,"path":390,"stem":391,"children":392,"page":403},"Docs","\u002Fdocs","docs",[393,397,400,401],{"title":394,"path":395,"stem":396},"Getting started","\u002Fdocs\u002Fgetting-started","docs\u002F1.getting-started",{"title":360,"path":398,"stem":399},"\u002Fdocs\u002Fcore-concepts","docs\u002F2.core-concepts",{"title":5,"path":382,"stem":384},{"title":178,"path":177,"stem":402},"docs\u002F4.edge-and-cloud",false,[405,407],{"title":360,"path":398,"stem":399,"description":406,"children":-1},"The vocabulary of TameChaos — Studio projects and Edge projects, facilities, topology nodes, connectors and containers, bills of materials, and the sensor arrays, experiments and runs the edge executes.",{"title":178,"path":177,"stem":402,"description":408,"children":-1},"Which responsibilities sit on the authoritative edge, which sit in the non-authoritative cloud, and where design-time authority sits — plus why distribution is publish-and-pull, never command.",1785465248328]