What is a world model for knowledge work?
A world model for knowledge work is a sourced, current map of a company and its market that AI agents query instead of guessing. Its three layers and an example.
A world model for knowledge work is a maintained, sourced map of a company and the world it operates in, which AI agents query instead of rebuilding that picture from tools on every run.
It holds the companies, people, places, regulations and events that shape the work, how they relate, what is true about each of them now and where each fact came from. It has three layers: the data that keeps it current, a graph of the things and their relationships, and the knowledge attached to those things.
Robots and video models learn a different kind of world model
In AI research, a world model usually means something else: a model that learns how a physical environment behaves so it can predict what happens next. A robot uses one to anticipate where an object will fall. A video model uses one to generate the next frames of a scene. Those models learn physics from pixels and sensor data, and what they know sits in their weights.
A world model for knowledge work holds a business instead of a physical scene: which hospitals are in the territory, which integrator serves each one, who changed role last week. It is not learned into weights. It is built from the company’s own records and from outside sources, and every fact in it can be read, checked and corrected. What the two share is the idea underneath: an agent acts better from a picture of its world than from whatever input arrived last. That is why we use the name, and why we add “for knowledge work”.
Some vendors now use “enterprise world model” or “world model for business” for related ideas. We say “for knowledge work” because the model is about the work, and the work depends on the world outside the company as much as on the records inside it.
It has three layers: the data, the graph and the knowledge
The data is everything that comes in from the company’s tools and from outside: the CRM, email, Slack, call recordings, public registries. Every fact derived from it keeps its source, so an address from a government registry and an address guessed in a rep’s note are not treated as the same fact. A fact that can change also records when it was true. When a person changes role, the new role supersedes the old one and the old one stays as history. A CRM field only shows the last value someone typed, which is how agents end up acting on stale facts, as Why coding agents work and company agents don’t shows.
The graph is the ontology filled in: the particular hospitals, integrators and people, each one a single identity whether it shows up as a CRM record, a registry entry or a name in an email thread. Without that, the same company in three systems is three companies, and the agent treats them that way. Things are joined by relationships that carry meaning and direction, such as “works at”, “installs at” or “regulated by”, which is what lets a signal travel from a regulation to a facility to the company that runs it to the open deal and its owner.
The agent’s job
Prepare Thursday’s call with St. Anna Hospital
Knowledge
- Supplied by Medcore, so the tender runs through them
- Tender likely in MarchAdded by this job, not yet reviewed
Graph
- St. Anna Hospital, hospital
- one hospital, from 3 records in 3 systems
- supplied by Medcore
- employs J. Peeters
- open deal Imaging renewal
Data · its sources
- CRM · St Anna Hosp.
- Email · procurement@st-anna.be
- Public registry · Sint-Annaziekenhuis vzw
The knowledge is what the company understands about those things, attached to the thing it describes rather than to the conversation it came from. A note about a regulation sits on the regulation, not on the call where somebody mentioned it. Agents write most of it and people review it, so an agent’s conclusion stays separate from accepted fact until a person or an agreed rule promotes it.
How it differs from a knowledge graph, an ontology and a context graph
These four terms get used as if they were interchangeable. They are layers of the same stack.
| Term | What it holds | The question it answers |
|---|---|---|
| Ontology | The kinds of things in a business, what each means, how they may relate and what can be done with them | What can exist here, and what can we do with it? |
| Knowledge graph | The particular companies, people, places and events, connected according to the ontology | What exists, and how is it connected? |
| World model for knowledge work | The graph, plus the data that keeps it current, the knowledge attached to each thing, time and a source on every fact | What is true about our business and its world right now, and how do we know? |
| Context graph | The slice one task needs: the things involved, their current state and the decisions already made about them | What does this piece of work need, and what was decided before? |
A knowledge graph is roughly the middle layer of a world model. The ontology is its legend. A context graph is what an agent draws from it for one task, plus the decisions made along the way. A world model is also not a wiki, a data warehouse or a vector index over documents. Each of those holds material about the company. None of them holds the things themselves, with one identity, a current state and a source.
An example from sales: a territory selling through integrators
At a deep-tech company that sells into hospitals through integrators, whether a hospital was worth a call depended on which integrator already supplied it. The CRM had no field for that, and the partner list was a spreadsheet of about 2,700 companies. We built the territory from government sources, hospital lists and integrator registries, normalised it and linked it to the CRM records they already had. The spreadsheet became 64 ranked accounts. The language model did not get smarter between those two numbers. It went from working on 2,700 strings to working on 64 things that exist.
The same model now feeds a meeting-prep agent that pulls previous calls, emails, deal history and similar companies before each external meeting, and a list of net-new accounts that rebuilds itself every morning.
Why it matters for AI agents
An agent is only as right as the picture it acts on. A world model changes what it can do in three stages. First correctness: the right company, the right person, the current role, the latest accepted fact. Then sight: connected facts show what no single source contains, such as a regulation change that touches several open deals. Then initiative: a standing goal, like that daily list, turns sight into work.
A smarter language model does not remove the need. It still does not know which integrators serve which hospitals in your territory or that the deal stages changed last week. That knowledge is not in its weights, and something has to hold it. The language model brings the intelligence. The world model brings the company.
Without one, agents rebuild the picture on every run and fill the gaps with what is typical, which is why AI agents give confident wrong answers.
Questions people ask
Is a world model for knowledge work the same as a knowledge graph?
Partly. A knowledge graph is its structure. A world model adds the data that keeps the graph current, time and a source on every fact, and a line between accepted facts and guesses. The longer answer is in Is a world model for knowledge work a knowledge graph?
Is it the same as a world model in AI research?
No. Research world models learn how a physical environment behaves from pixels and sensor data, and hold what they learn in their weights. A world model for knowledge work holds a business, is built from records and outside sources, and every fact in it can be read, checked and corrected.
Does it replace the CRM?
No. The CRM, email and Slack keep doing their jobs and feed the model. The model holds what none of them hold alone: one identity per thing across systems, the relationships between things and the history of how they changed.
How does a company get one?
It is built around the work you want agents to do, starting with the ontology for that work and the sources that fill it, then grown as more work moves onto it. At Ortelian we build it during a deployment, and it runs on our platform, hosted in the EU, as part of the engagement.
