In every enterprise, the same thing exists in fifty places. A customer in the CRM. A debtor in finance. A user in operations. A signature on a paper contract, each shaped by the system that holds it, each speaking a different dialect.
We've spent two decades writing translators between them. We call them integrations, mappings, ETL, master data management, canonical models. None of them survive past two systems. They rot the moment something new connects.
The translator approach is finished. There is a different path: don't model. classify.
UDF holds that everything in the enterprise is one of Location, Entity, Asset, Product, Event, or Document. No more. No less. Six fundamentals, what the world actually contains.
Every record from every system is given a primitive, and becomes a node in one centralised graph. Queryable by humans, BI, agents, anything that asks.
UDF is Arero7’s product, in production since February 2026. Three capabilities stand on one graph; start with the one that hurts most.
PDFs, emails, spreadsheets, XML, EDIFACT. Flows understands whatever your partners send and delivers clean orders to your systems, on a ledger where nothing silently disappears.
BI, KPIs, customs audit files, IMO manifests. Define a report once and the graph unfolds it into any format — the same truth in every document, every number traceable.
Agents that stand on your graph and answer with your actual records, not approximations. Every answer points back to the evidence it came from.
Every record from every system, classified into six primitives and connected into one world model. Everything above is a view of it.
Explore →The premise is simple. Believing it is the work. Once accepted, the data layer collapses, every record in every system fits exactly one primitive, and every primitive carries shape, behaviour, and a place in the graph.
Where it is. Anywhere with a coordinate, address, region, route, or geofence, physical or virtual.
Who or what acts. People, organisations, agents, departments, customers, anything that holds a role.
What persists. Machines, buildings, accounts, inventory, code, IP, anything that has state.
What is offered. Services, goods, plans, subscriptions, contracts, value exchanged with the world.
When something happens. The connective tissue. An order, a delay, a payment, a query, a delivery.
What is recorded. Invoices, contracts, manuals, emails, tickets, runbooks, the artefacts of business.
Once classified, a record finds its place. Connections form between what was scattered. Queries traverse the graph, not the systems.
"Where is unit 4019, who serviced it last, and which document covers it?" Three primitives, one query, no joins.
UDF does not stand alone. It is the third layer of a four-layer stack, counsel above it, grammar beneath it, agents on top of it. Each layer has exactly one job.
The parent and the voice. Advisory and build for the intelligent enterprise, counsel for leadership, architecture for what is missing. Everything below carries its signature.
arero7.com →The ontology behind the six. Location, Entity, Asset, Product, Event, Document, a complete grammar for what an enterprise contains. LEAPED decides what a record is.
leapedontology.com →The platform that puts the grammar to work. Every record from every system, classified and connected into one queryable graph. The field the rest stands on.
→ you are here
A flock of agents that move through the graph, weaving threads between sources, surfacing what matters, taking work off the table. The first bird is a swallow.
intelweaver.com →