Engineering IR · Compiler · Architecture
What an Engineering IR provides that CAD files do not
An intermediate representation makes engineering facts deterministic, addressable and reusable across review, procurement, service and agent workflows.
Written by WorldIR · Reviewed by WorldIR Engineering · Updated 26/08/2026
Compilers succeed because later tools do not repeatedly reinterpret source syntax. They consume an intermediate representation with stable meanings. WorldIR applies the same principle to engineering assemblies.
The source may be STEP, STL, a BOM, a drawing or a manual. Each format contains useful evidence and each has different failure modes. Engineering IR gives downstream applications one typed surface without pretending those sources are equivalent.
Determinism before dialogue
Part hashes, dimensions, feature recovery and interface relationships are deterministic compiler work. Running the same inputs and pass versions should produce the same identifiers and artifacts. This makes results cacheable, testable and replayable. An agent is then useful for tasks with genuine ambiguity—researching current suppliers, comparing conflicting documents or preparing a proposal for human review—not for redoing arithmetic.
Evidence stays attached
A fact without a locator is difficult to audit. WorldIR facts retain their source asset, revision and location. Search returns evidence IDs. A cited answer may use only those IDs and must abstain when the evidence does not settle the question.
One representation, several workflows
The same IR can support an assembly-readiness report, a reconciled BOM, a DFM finding, a robot-cell requirement, a sourcing plan or a service package. These are not unrelated AI features. They are projections of the same fixed engineering boundary.
That is what makes the representation strategically important: each new application improves the value of the compiler and evidence graph instead of creating another disconnected interpretation of the original CAD.