Why Entity Models Miss the Most Important Thing: Movement

The dominant paradigm in business intelligence is entity-relationship modeling. Map the nouns. Draw the connections. Visualize the structure.

It works. Palantir built a $400 billion company on it. But it has a blind spot that becomes critical when you move from enterprise data to knowledge work.

Entity-relationship models map what exists. They don't map how value moves.

Nouns vs. Verbs

"Supplier A connects to Manufacturer B" is an entity-relationship statement. It tells you the structure exists. Useful. But it doesn't tell you:

- That the handoff between them costs $2 million in delays per quarter - That value is leaking because the information flow is asymmetric - That three other organizations solved this exact bottleneck through different mechanisms - That a rights constraint on one resource is blocking the entire flow

The nouns are necessary. The verbs are where the actionable intelligence lives.

REA: The Accounting Ontology

REA — Resource-Event-Agent — was originally designed as an accounting ontology. Its purpose: capture economic exchange with enough granularity to model how value actually flows through a system.

Resources are classified across 16 dimensions. Not just "what is it" but what can it do, who has rights to it, what constraints apply, where it's currently stuck, and what would unlock it. A "partnership opportunity" in a standard entity model is a node with a label. In REA, it has a rights structure, a constraint profile, a flow state, and a friction score.

Events capture the verbs — 23 value flow action types that map the movements of business. Transfer, transform, exchange, commit, release, defer. Each event has a timestamp, participants, and measurable effects on the resources involved. Not "Supplier A connects to Manufacturer B" but "Supplier A transferred 400 units to Manufacturer B on March 3rd, triggering a quality review that created a 6-day delay."

Agents are the actors — people, organizations, automated systems. Each agent has preferences, constraints, and a scored relationship to the resources they hold or need.

Scored Opportunity Maps

When you model an ecosystem with REA instead of entity-relationships, the output changes fundamentally. Instead of a static structure diagram, you get a scored opportunity map.

Every value flow is scored for friction, blockage, and leakage. High-friction flows are where intervention has the most leverage. Blocked flows are where value is trapped. Leaking flows are where value is being lost without anyone noticing.

We overlay this on a Business Model Canvas to create strategic visualizations. Revenue streams, cost structures, key partnerships, and customer segments — all annotated with flow scores.

The pattern we see in every engagement: organizations sitting on value they've already created but can't access. The resources exist. The agents exist. The connections exist. But the flow is blocked at specific, identifiable points.

Entity models tell you what's there. Value flow tells you what to do about it.