Runs
All runsPolicy
Change the rulesThe day, and the systems
How this Studio is put together: the three planes, live
Agent plane
The Agent service runs the model for an agent node, with one tool in its hand: hand in a proposal through the Bridge. It holds no key to any company system.
⇄
The Bridge
Five door calls, one run token per node, every crossing recorded: the brief, prepared data, a declared read, a search, the proposal.
Enterprise plane
The Enterprise service: the conductor runs the map, the code checks judge, people approve, the connectors act on the company's systems.
The company's systems, behind the connectors
How Studio works, in four steps
1Draw or describe a mapOn the canvas: nodes in two lanes, parts from the library, links between them. Or a few sentences, and the builder's model draws it. The map rules check as you go.
2Publish itA version the Enterprise service can run; it cannot be changed afterwards, a change is a new version.
3Run itThe conductor runs the map: the agent proposes through the Bridge, code checks judge, a person approves, the connectors act. Shadow sends nothing until a person turns it off.
4Change the rulesThe company's own rules, typed in Excel, imported and published as the next version; the next run is judged by it.