OTO
oto

A graph per domain, and the mesh

The centralisation trap is one graph for everything, owned by no one, right about nothing. OTO takes the opposite shape: one graph per domain, owned by the people who know it, joined by shared vocabulary.

The concierge, across graphswhich domain answers this question; its answer, with its source
Claims · Platform · Organisation · each productone graph per domain, its own ontology, its own curators, its own store
Ontologies that extend one anotherevery one rests on oto-core, so every fact has the same shape
Registriesthe public catalog, and a private registry per company
The enterprise knowledge mesh: graphs that compound because they share a core vocabulary, not a central store.

A domain is a bounded context

A domain in the company's sense, claims, payments, the platform, a product, is a bounded context in the design sense: a place where words have one meaning. Each gets its own oto project, its own ontology, its own curators, its own store. The claims graph says what a claim is in claims' words; the finance graph does not have to agree.

Claims
auto-claimspolicies, coverages, claims, procedures, roles
curated byclaims operations
Platform
software-architecturesystems, components, datastores, decisions
curated bythe platform team
Organisation
organization-processunits, roles, processes, policies, measures
curated byoperations

Ontologies are how graphs join

Every ontology extends oto-core, the temporal vocabulary and the one class every fact cites, a Document. A company's ontology extends a catalog one and adds its own words; a pack embeds the ontology with everything it extends. Because every graph shares the core, a fact in any of them has the same shape: a status, a validity window, a source. That is what lets a question travel across graphs.

An ontology is versioned. A project remembers which release it started from; oto status says when a newer one exists, oto ontology diff classifies the change and counts the nodes it touches. Domains evolve their vocabulary without breaking one another.

The catalog, and private registries

The public catalog holds the ontologies and packs anyone can start from. A company runs its own registry, a git repository, for the domains that are its own. Both are Claude Code marketplaces, so a pack installs the same way from either.

The mesh is OTO

oto builds and serves one graph. The mesh is what OTO builds over many: the concierge that takes a question, decides which domain answers it, asks that graph through its query tools, and returns the answer with its source. Studio's spaces are where a team sees its domain and the domains it depends on. Cross-graph search and the concierge over several graphs are OTO; the engine's concierge skill is the single-graph version, which says where a project stands and what comes next.