Isaac Correa · Madrid

How we build a company’s ontology

In September 2026 we published the method Hellomatik uses as a technical report with a DOI, deposited in two independent repositories and indexed under my ORCID. This page says what is in it and where to read it.

Isaac Correa, co-founder of Hellomatik, in Madrid
Isaac Correa in Madrid. The method described here is published as a technical report with the DOI 10.5281/zenodo.22647735.

Why a DOI and not a whitepaper

A technical report can be cited, checked and taken apart. A DOI puts a fixed, dated version of the text in a repository that is not ours, so anyone can quote it and it does not depend on us keeping a link alive.

The people we want reading it are operations directors, systems people, the person in a company who is quietly responsible for the ERP. They read papers.

What is in it

The report goes layer by layer. It starts with the data of the company and which system each piece comes from. Then the rules the company already decides by, written so that an agent can apply them rather than guess. Then the actions: what can be done, with what parameters, leaving what record. And last, permissions: who, or which agent, can go how far, and which actions wait for a signature.

The four layers the report goes through, in order Four layers, written in this order: the data of the company and which system each piece comes from; the rules the company already decides by; the actions it may take; and who may approve what. An agent acts only through the layer above it, and each layer can only refer to the one below, so nothing can be automated before what it rests on has been written down. The agent answers, watches and executes — but only through what is below acts through the four Permissions who may approve what, with a name and a date Actions what the company may actually do in the world Rules what it already decides by, written in one line each Data and which system each piece of it comes from The order it has to be written in: each one rests on the one below it. Nothing sits below this one.
The order the report goes in. Nothing above can be automated before the thing it rests on has been written down — which is why the first week of this work is a conversation and not an installation.

It also describes what we have running today: four systems in production, including a logistics one with 24 rules over a live warehouse and a B2B sales one that recalculates 29,000 customers. A method with its scope written down is a method.

Title
How we build a company’s ontology (2026)
Author
Isaac Correa
Length
26 pages
PDF
Read the report (PDF)
DOI
10.5281/zenodo.22647735
Also on
SSRN — posted 10 September 2026, 26 pages. Posted means it is in the SSRN library and can be downloaded; it does not mean anybody reviewed it.
ORCID
0009-0003-0657-4419

The story of how the method came about is here.

Read more

How Hellomatik started — the problem the report is an answer to, told as it happened.
Press kit — bios you can paste, photographs, and every fact with its source.

The timeline — every date with the place you can check it.

Photographs — the pictures that exist of him, free to reuse with attribution.

What selling taught me — three hundred commissions, and the lesson underneath.
How I work on a product — the order I trust, and two months screen by screen.

Your company already has rules — what happens in the first week of automating a business.
From a seven-dollar dashboard to Hellomatik — the whole story with its dates.
The questions people ask about Isaac Correa — fifty-six short answers, each with a source.
Copy until you find creativity where there is none — how I think about innovation.
The machine of the future — written in November 2025, on what the next tool is.
Hellomatik and Kodalogic — what each company does, and where to check it.
Where others have cited this work — the two places that used it as a source.