01
THESEUS
The ontology system.
The map of how your business actually works. The real things in it, what each one carries, how they connect, and what is allowed to happen to them. Everything downstream is built from this.
02
THE DIFFERENCE
No product sold to thousands can be a map of yours.
Your software should be a map of your business. A product built to sell to thousands of companies cannot be that map for any one of them, which is why you end up changing how you work to suit the software. We build the map from how the work actually happens on your floor, and the system gets built from the map.
03
WHAT IT HOLDS
Four things. Everything downstream is built from them.
The first three are what your business is. The fourth is what it can do.
01
OBJECTS
The things the business is made of. A job, a customer, a vehicle, a crew, a quote.
02
PROPERTIES
What each one carries. The fields that matter, and the ones that turn out not to.
03
LINKS
How they connect. Which job belongs to which customer, and which crew is allowed to touch it.
04
ACTIONS
What is allowed to happen. Who can move a job forward, and what has to be true before they can.
IN PRACTICE
Work happens in whole moves.
A person marks the job finished. Everything that has to change changes together, and the conditions that must be true first are declared once in the model instead of living in whoever trained them.
It runs on live data.
The map holds the real jobs, the real vehicles and the real crews. The business is operated through it, which is the difference between a model and a diagram on a wall.
It gets more valuable the longer it runs.
Every decision your people make is recorded as they make it. What begins as a description of how the work should go becomes the record of how it actually went.
04
WHAT IT IS FOR
THE MODEL IS THE MACHINERY.
An ontology gives your business proper nouns. A job, a crew, a vehicle, a quote: each one defined once, with the rules about what is allowed to happen to it declared alongside it. Everything above reads from that definition and is executed against it, which is why it is worth authoring before a single screen exists.
EVERY SCREEN AGREES
Two surfaces showing a vehicle are showing the same vehicle. Consistency stops depending on whoever wrote the second query.
NEW SURFACES GET CHEAP
A screen is assembled out of things the model already knows, so most of the work is configuration over a shared vocabulary instead of a new codebase.
THE ENGINE KNOWS NOTHING ABOUT YOUR TRADE
Only your model does. That is why the same platform can run a wrap shop and a clinic without either one bending to fit the other.
