Skip to content
/01 INDUSTRIES

The entities differ. The architecture does not.

When people compare industries, they focus on what makes them different. Healthcare treats patients. Mining extracts minerals. Telecommunications companies connect people. These differences are real. They matter.

Yet they obscure a deeper truth. Every organisation, regardless of industry, faces exactly the same fundamental challenge. It must understand itself well enough to make better decisions.

A hospital possesses patients. A mine possesses production equipment. A logistics network possesses shipments. The entities differ. The architecture does not. Only the vocabulary changes.

Which is why eight industries is a plan rather than a boast. The architecture is built. The vocabulary is declared. Each industry below says plainly which of those two things is already true for it.

HEALTHCARE
RUNNING TODAY

Which ward is actually full

Healthcare experiences many disconnected episodes where a patient experiences one continuous life. Built today: occupancy counted per ward-stay rather than credited whole to the ward that admitted, medicine descriptions resolved to codes, and every AI-written change carrying a named approver.

WHAT IS BUILT
SUPPLY CHAIN
RUNNING TODAY

The alert that carries its own instruction

One disruption propagates through the entire network. Built today: an exception arrives with the action it recommends, becomes an instruction owned by a named person against an SLA, and closes against a fixed list of outcomes — so adherence is computed, not felt.

WHAT IS BUILT
TELECOMS
ON THE ROADMAP

What was instructed against what was done

Telecommunications connected people. It is now asked to account for its own field operations with the same precision. Field work orders, asset condition and SLA adherence, where what was instructed and what was done are two separate recorded facts.

HOW IT GETS ADDED
UTILITIES
RUNNING TODAY

An exceedance with an owner, not a red cell

Water and wastewater today: lab results read against permit limits, flows, energy and chemical cost per works, and a discharger's compliance history visible while the contact person behind it stays masked. Electricity and municipal billing are not built.

WHAT IS BUILT
RAIL
ON THE ROADMAP

From a defect to the decision it forced

Rail operators optimise trains. Ports optimise vessel turnaround. Each is rational alone and the corridor still fails. Rolling stock availability, maintenance compliance, and a chain from a detector reading to the action someone took that survives a regulator's enquiry.

HOW IT GETS ADDED
MINING
ON THE ROADMAP

Proving who was cleared for what

A mine is not a collection of departments. It is a living operational organism, where every decision influences dozens of others. Section 54 stoppages, contractor competency and medical fitness, and the authority behind a decision shown without assembling it from three spreadsheets.

HOW IT GETS ADDED
RETAIL
ON THE ROADMAP

Stock loss with a name attached

Retailers forecast demand while the loss happens on a shop floor nobody is watching in time. Shrinkage and pricing compliance across branches, where an exception raised at head office becomes an instruction a specific store manager owns and closes.

SEE THE RETAIL BRIEF
AGRICULTURE
ON THE ROADMAP

Traceability an export auditor will accept

Agriculture is more than farming: the journey from seed to table spans dozens of organisations, each making decisions that influence the others. Cold chain and consignment history written to a ledger with no update path, so what was recorded at the time is what an auditor sees.

HOW IT GETS ADDED
WHERE WE ARE FURTHEST ALONG

Three of the eight are built and running, on one unchanged core. That is not a claim about ambition — it is the evidence that the other five are declarations rather than rewrites.

HEALTHCARE

Hospital groups and clinical operations

Bed and ward occupancy counted properly — a stay crossing three wards counted in all three, not credited whole to the ward that admitted. South African ID validation. Free-text medicine descriptions matched to NAPPI codes. Identifying fields masked by role, so a bed scheduler sees a ward while a clinician sees a patient.

Being honest about the edges: our SA ICD-10 edit rules are written but not yet signed off by a clinical coder, and the full NAPPI catalogue is licensed and loads once that licence is in place. We will not run either against your live data until then.

READ ABOUT THE BED WORK
ONE STAY, THREE WARDS STAY WARD A WARD B WARD C DAY 1 DAY 8 CREDITED TO ADMITTING WARD A8 B0 C0 COUNTED PER WARD-STAY A2 B3 C3 BED-DAYS PER WARD. SAME STAY; THE RECEIVING WARDS WERE INVISIBLE.
LAB RESULTS AGAINST PERMIT LIMIT PERMIT LIMIT EXCEEDANCE → EVENT, OWNER ASSIGNED
UTILITIES — WATER AND WASTEWATER

Treatment works and discharge compliance

Lab results ingested and read against permit limits, where an exceedance becomes a recorded event with an owner rather than a red cell in a spreadsheet. Flows, energy and chemical cost per works. A discharger's compliance history is visible to an analyst while the contact person behind it stays masked — POPIA reaches juristic persons here too.

FROM ALERT TO OWNED, CLOSED WORK ALERT with recommended action INSTRUCTION named owner against an SLA CLOSED AS ■ as instructed ■ with variance ■ not executed A FIXED LIST, NOT A COMMENT BOX — SO ADHERENCE IS COUNTED
SUPPLY CHAIN AND INVENTORY

Alerts that carry an instruction, not just a colour

Each alert arrives with the action it recommends. Issuing it creates an instruction against a named owner with an SLA, and closing it records an outcome from a fixed list rather than a comment box — so “83% executed as instructed, and here are the three reasons for the rest” is computable instead of anecdotal.

/02 HOW THE NEXT FIVE GET BUILT

Your industry is a declaration, and we have already tested that claim three times.

Nothing in the engine knows what a hospital is. The things your business is made of — and what may be done to them, by whom, and with whose approval — are written down in a registry, and the database tables, the permissions and the API are generated from what is written there.

That is why a wastewater treatment works and a hospital ward already run on the same core with no changes to it. The water pack declares thirteen kinds of thing healthcare has never heard of. Not one line of the engine moved to accommodate them. A railcar, a work order, a consignment and a shift roster are the same kind of exercise.

So the open question for rail, mining, telecoms, retail and agriculture is not whether the engine can carry them. It is how your data actually arrives, what your approval rules turn out to be once written down, and which of them are genuinely enforceable rather than merely wished for. That is a scoping conversation, and we would rather have it with you than print a timeline on a web page.

WHAT IS ALREADY BUILT, WHATEVER YOUR INDUSTRY
  • The governed write path and the audit ledger
  • Proposal and approval, including that the approver cannot be the proposer
  • Your own database, and access enforced by the database itself
  • Role-based masking of identifying fields
  • The bridge that lets a model take the same actions a person can, through the same gate
WHAT IS NEW FOR YOU
  • The things your business is made of, and the actions allowed on them
  • Your approval thresholds and who holds them
  • Checks specific to your rules and your regulator
  • The binding to however your existing systems hand over data
/03 WHAT THIS IS FOR

Organisations no longer compete on information. They compete on understanding.

For decades, enterprise technology has focused on recording work. A hospital, a mine and a rail network each run dozens of systems that record faithfully and understand nothing. Every system performs its individual function exceptionally well. Very few understand the enterprise as a whole.

The consequence is the same everywhere. Executives wait weeks for answers that should take minutes. Knowledge disappears when experienced people retire. Departments optimise locally while the organisation underperforms globally. Artificial intelligence is deployed onto fragmented data, and produces fragmented intelligence.

Our premise is different. The problem is not insufficient technology. It is insufficient organisational understanding.

So we start where understanding is provable rather than asserted: a decision your people make over and over, made inside a system that records what was decided, on whose authority, and what it changed. That record is the beginning of an organisation that can understand itself. Everything else is built on it.

Yours is on the roadmap. Move it up.

The five ahead of us get built in the order that serious conversations arrive in. Bring the decision your people make over and over that nobody can fully account for afterwards — thirty minutes, the live system, and a straight answer about where your industry actually stands.

Talk to us