Make your brand context legible to agents
The Ontological Brand Graph defines what the objects in your workspace mean and how they relate. A brand owns channels, an asset has channel branches, and a saved source can inform new work. Those relationships give agent reasoning a structure it can query.
Build your brand space
Describe the work with a shared vocabulary
Objects have stable identities and a declared workspace or brand scope. Relationships describe ownership, lineage, and the connections between the work. A channel branch remains part of an asset, with its own target and history.
People and agents can therefore refer to the same object. Explorer makes the relationships visible, while Maris uses declared queries to inspect the relevant part of the workspace.
Make the ontology operational
The ontology defines queries for reading relationships and actions for changing business state. Each operation has a declared input, authority requirement, and result contract.
An agent can ask for an asset’s branches or a channel’s performance using those contracts. Changes pass through the owning domain service, which preserves the rules of the object being changed.
Keep the graph connected to durable truth
Transactional state remains in the canonical data store. The graph projection is a rebuildable view used by admitted relationship queries. This keeps visual exploration and agent queries tied to the same underlying work.
An asset’s connection to a source or destination can therefore explain where material came from and where it is going. Branching and attributable history make those relationships useful during authoring and distribution.
Read about asset branching