How we build a company's ontology: the method Isaac Correa published with a DOI

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 is what is in it and where to read it.

Isaac Correa, founder of Hellomatik, in Madrid
Isaac Correa in Madrid. The method described here carries 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.

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.

Where to read it

There is a second, shorter piece on what the next tool will need from us: The machine of the future, DOI 10.5281/zenodo.22671771.


The full page for this report is on Isaac Correa's own site. The story of how the method came about is here, and the places that have cited it are here.

Comments

Popular posts from this blog

Six pages I added this week, and what each one is for

Who cited Isaac Correa, and what they were actually looking for

Isaac Correa: who I am, and where every fact can be checked