An intelligence layer above agents. Not an agent and not a framework — an intermediate layer that takes a task in natural language and returns a verifiable artifact: a typed tree of meaning with computed confidence.
The knowledge is already inside the model; what the model lacks is the discipline of interrogating itself. So here the model does not "think" — it answers. Intelligence is moved outside: into the interrogation procedure and into the graph where answers accumulate. Two consequences carry the whole design:
| Alphabet | Members |
|---|---|
| Node types (16) | MECHANISM · PROCESS · FLOW · ENTITY · PLACE · STATE · EVENT · CONDITION · CONSTRAINT · EFFECT · RISK · FACT · CLASS · QUESTION · CONCLUSION · GOAL |
| Edge types (18) | DECOMPOSES_TO · HAS_PART · PERFORMS · PRODUCES · CONSUMES · FLOWS_TO · LOCATED · AFFECTS · CAUSES · TRANSFORMS_TO · REQUIRES · INSTANCE_OF · KNOWN_FOR · INTERSECTS · ASKED_ON · ANSWERS · CONCLUDES · EVALUATED_AS |
Every edge type declares which node types it may legally connect. An illegal edge is a parse error, not a footnote. The lists are closed in the moment but not frozen forever — extension is an explicit operation, never a side effect of parsing.
An edge carries not the fact of existence but the degree of necessity: certain 1.0 · likely 0.7 · conditional 0.5 · possible 0.4 · rare 0.15. A conclusion's confidence is the product of weights along its path. "Probably mold" is produced by arithmetic — not by a hedge the model added.
The procedure interrogates the model with a closed set of operators; each builds a specific kind of edge.
| Operator | Question | Builds |
|---|---|---|
| decompose | What is this mechanism made of? | DECOMPOSES_TO |
| processes | Which processes run while it works? | PERFORMS |
| products | What does the process produce? | PRODUCES |
| routing | Where does the flow go? | FLOWS_TO |
| spatial | Where is the object located? | LOCATED |
| timeline | What does the state turn into over time? | TRANSFORMS_TO |
| abstract | What is this a special case of? | INSTANCE_OF + KNOWN_FOR |
| impact | How bad is it, and is it reversible? | EVALUATED_AS |
| precondition | Under which conditions does it happen? | REQUIRES |
| interaction | What happens when two branches meet? | CAUSES |
The model answers as well as it understands what it was asked about. "Where does the condensate go?" in a vacuum yields an abstract answer about drainage; the same question with a path and a scene yields an answer about this installation. The context block is assembled from the graph deterministically — the same graph produces a byte-identical block, otherwise there is neither reproducibility nor cacheability. The block carries: the goal of the parse, the scene, the participants, the path to the node, what is already known about the node, and what was found nearby on the same step.
| Field | Contents |
|---|---|
| graph | The full object model; a flat, diffable JSON serialization. |
| conclusions | Findings: text, the reasoning chain, confidence, risk. |
| validation | Mechanical composition check — ok plus the list of issues. |
| trace | Every step: what was asked, what came back, where branches closed. |
| stats | Graph size, questions asked, stop reason, token spend. |
The layer does not manage execution: it hands over the artifact, and other agents execute it. The reverse channel — execution results refining the parse — is the next step.
An air conditioner, a balcony, a sofa. The answer ("mold") is hardcoded nowhere: the mock provider only answers local questions and does not know the task. The engine must assemble the conclusion itself — and does, with its confidence computed as the product of edge weights along the path.