/ explore · architect
Six layers between a systemand something you can use.
Inferrex does not connect systems and hope. It builds understanding in order — what exists, what shape it has, what it means, how it relates, what follows from that, and what you can then do.
/ the architecture
Each layer is only possible because the one beneath it exists.
Most integration tooling starts at the last layer and works backwards, which is why it has to be told what everything means. Inferrex starts at the first.
1 · Systems
APIs, applications, databases and services. The things that already exist, discovered rather than declared. Across 234,373 vendors catalogued and 1,941+ providers fully specified.
2 · Structure
Schemas, fields, types and the shape of a payload. What a system is made of, read from what it publishes rather than from documentation about it.
3 · Meaning
Concepts, classifications and canonical representations. A field called `cust_ref` and one called `customerId` stop being two strings and become the same idea, with 1,733 canonical keys behind the judgement.
4 · Relationships
Mappings, dependencies and connections. Which systems touch which, where the same entity appears twice, and what breaks if one of them moves.
5 · Intelligence
Analysis, recommendations, opportunities and change detection. Understanding that notices something rather than waiting to be queried.
6 · Outcomes
Integration, automation, governance, migration and AI. The layer everything else was for, and the only one most tools ever show you.
Diagram required
The six layers, stacked
Systems → Structure → Meaning → Relationships → Intelligence → Outcomes, as a stack where each layer visibly rests on the one beneath. Brief 1 §18 wants progressive reveal; this is the static form that has to be readable without JavaScript.
4:5
/ the argument
You cannot skip to the outcome and keep the guarantees.
A connector built directly at layer 6 encodes one assumption about layer 3 — what a field means — and hides it inside itself. When the field changes, the assumption is wrong and nothing says so. The integration does not fail loudly; it moves the wrong value.
Building the layers in order means the assumption is written down, at the layer where it belongs, once, for every outcome that depends on it. Change arrives at layer 2, is re-reconciled at layer 3, and every outcome above it inherits the correction without being rewritten.
One understanding. Multiple outcomes.
/ see it
The layers are not a diagram. They are running.
The Universe
Layers 1 and 4, drawn. Every comprehended system, positioned by how deeply it is understood.
ExploreThe Corpus
Layers 2 and 3, catalogued. The knowledge base the reconciliation reads from.
ReadComprehension
How layers 1 to 3 are actually built from a system that was never designed to explain itself.
ReadPoint it at something and watch the layers build.
Development is self-directed. Bring an API nobody has documented properly and see how far up the stack it gets.