/ platform · comprehension
How a system that was never designedto explain itself is understood.
Understanding what a system and its fields actually mean. A specification tells you a field is called cust_ref and holds a string. It does not tell you that it is a customer identifier, that it corresponds to a differently named field in four other systems, or that it changed type two versions ago.
/ what arrives
Four fields. Names that are abbreviations.
{
"cust_ref": "string",
"created": "string",
"amt": "number",
"st": "string"
}Types that describe storage rather than meaning. No relationships. No history.
/ what Inferrex adds
Six things the specification does not carry.
Meaning
cust_ref is a customer identifier. amt is a monetary amount, and the currency is carried elsewhere. st is a status against a known enumeration.
Relationships
Each field resolves to a canonical concept, and through it to every field in every other comprehended system holding the same concept.
Confidence
How certain the classification is, and on what basis. Inference is published with its confidence, not laundered into fact.
Provenance
Where the understanding came from: a crawled specification, a vendor submission, or a named contributor's correction.
Version
Which release of the interface this understanding describes, and what changed from the last one.
Canonical concept
The shared key that makes the field comparable to anything else in the corpus.
The output isn't a connector. The output is understanding.
/ why it compounds
A connector is worth one integration.
A comprehended system is worth an integration with every other comprehended system, and the total grows with the square of the corpus. That is the whole economic argument, and it is why The Corpus is the asset rather than the connector count.
Once the schema is understood, API and schema mapping relates it to every other system. Self-healing integration watches for the schema to change.
Bring an API nobody has documented properly.
It is the fastest way to see the difference between reading a specification and understanding a system.