The Studio
The Studio is every view over the graphs, in one design system, and the portal that puts them together; underneath, the mesh connects the graphs. Its views today are the explorer and the reader the engine serves, and the views a pack ships for its domain; they are the engine's built-in ones, dark today, and they take the Studio's design system next. OTO Studio, the portal shown on the front page and in alpha, is the face for a whole organisation: discover a domain, validate a graph, see one truth in two faces, the business flow and the graph, and organise the work in spaces.
the explorerevery entity with its status, dates, source and connections; the graph drawn; served at / by oto serve --httpthe readerthe page-shaped view, for readers who want prose: --view readeryour viewa web app you pass, its data files generated from the graph as its app.json saysthe previewthe graph as it would be with every proposal in, rebuilt as you author: --watcha static siteoto build --target site, hosted anywhereOTO Studiothe portal: domains, products through their lifecycle, journeys, bounded contexts, the event flow beside the graph, spaces. In alpha: it runs on a sample organisation and is shown on the front page; not yet installablepack viewsa view per domain that deserves its own face, shipped in the packThe explorer and the reader
The explorer is the generic view and the default. It is deliberately neutral in what it shows: it shows any domain's graph the same way, so a reader learns it once. The reader turns the same data into pages, for a domain where prose reads better than a graph. Both are views under the same contract, and a pack ships its own when the domain deserves one.
OTO Studio
Studio reads the graphs the engine serves; it adds no facts of its own. The front page shows a product of a sample insurer through all six phases.
Its pages
The explorer and the reader. The product lifecycle in the Studio. Views. The pending lane, the preview and watch mode. The HTTP front end. oto serve.