01
Industrial geometry is not just an image
A CAD model may be rendered as pixels, but the engineering object behind those pixels contains much richer information. Solids have faces and edges. Assemblies have occurrences and transforms. Members have finite extents and axes. Features have dimensions and locations. Connections exist in a spatial hierarchy.
When an AI workflow ignores that structure and treats the model only as an image, it voluntarily discards some of the strongest evidence available.
Vision remains useful for photographs, field observations, scanned environments, and situations where native geometry is unavailable. But when exact engineering geometry exists, the system should extract what can be measured before asking a probabilistic model to interpret the remainder.
02
Deterministic first does not mean AI last
A deterministic geometry layer is not an argument against machine learning. It is an argument for assigning different tools to the parts of the problem they handle best.
Geometry kernels, computational geometry, graph algorithms, coordinate transforms, tolerancing rules, and explicit engineering checks are good at repeatable calculations. Learned models are good at interpretation, comparison, retrieval, language interaction, ambiguous classification, planning, and combining incomplete context.
The architecture becomes stronger when those capabilities are composed rather than blurred together.
03
What the geometry layer should preserve
The output should be more than a list of measurements. A useful physical representation needs identity and provenance so downstream reasoning can trace a result back to its source.
NIST's digital-thread research highlights persistent identifiers, semantic product and manufacturing information, geometric/topological representation, and traceability as continuing requirements for model-based manufacturing. NIST has also specifically studied universally unique identifiers as a way to track engineering characteristics across lifecycle systems.
That suggests a geometry intelligence layer should preserve both the engineering result and the path used to obtain it.
04
Canonicalization reduces ambiguity
One recurring geometry problem is that the same physical shape can appear at different positions and orientations. If every downstream tool reasons directly in arbitrary assembly coordinates, comparisons become unnecessarily difficult.
Canonical coordinate systems create a normalized frame for geometric comparison. A structural member can be translated and rotated into a stable local representation while preserving the transform back to its original location.
This makes questions such as 'are these two parts geometrically equivalent?' or 'which end contains this feature pattern?' easier to answer consistently. It also separates intrinsic shape from assembly placement.
05
Traceability is a technical feature
In industrial AI, explainability cannot be limited to a model-generated paragraph. A useful explanation may need to expose the source entity, measured geometry, transform, rule, and inference that led to a conclusion.
NIST's STEP File Analyzer demonstrates the value of exposing structured entity and attribute information from standardized product data. The larger principle is that engineering information becomes more useful when it can be inspected and validated independently of the interface presenting it.
GeometryLab is being developed around this principle: structure the physical facts first, preserve the evidence, and make the resulting representation available to reasoning systems through explicit queries and tools.