One coherent model of how the business actually runs.
People, work, metrics, events, risks and actions — connected. Every recommendation, brief and decision is grounded in the same relationships.
Why this exists
Three things the model gives every other surface for free.
Atlas, Briefs and Studio all reason in the same nouns and verbs — no two dashboards disagree on what a 'team' is.
Atlas references this modelMetric A moves metric B moves goal C — the chain is explicit, so impact is traceable end-to-end.
Open impact tracingEvery live recommendation declares which business goals it supports. Drift becomes visible.
View business goalsEntity catalog
The vocabulary the platform reasons in.
Top-level enterprise scope.
Strategic operating division.
Customer-facing service line.
Cross-functional initiative.
Geographic operating territory.
Physical or virtual delivery location.
Coached unit of agents.
Front-line leader of one or more teams.
Individual contributor.
End party served by the operation.
A single customer touch.
A unit of work spanning interactions.
Quantitative measure of an operation.
Strategic outcome the enterprise commits to.
A potential adverse outcome being monitored.
A committed leadership choice.
Work undertaken to achieve a decision.
An engine-proposed action with evidence.
Something that happened in the operation.
Relationship grammar
How entities relate. The model speaks in subject · verb · object.
Where this model shows up
Pick any KPI · see what moves it and what it moves.
The strategic outcomes every recommendation supports.
The v7.0 graph this model extends.
Reasons in the model's vocabulary, every reply.
Simulations propagate along these dependencies.
Patterns and outcomes write back into the model.