0.1 support matrix

Legend: Yes is release-gated public behavior, Partial is usable with an explicitly documented weaker contract, and No is not advertised.

​

Modeling

​

Topology

Construction and complete history are separate columns conceptually. A stock OCCT fillet may construct successfully while downstream semantic lineage is partial.

​

Product structure and analysis

These evaluator-level features work with either kernel when all underlying geometry features are supported:

• parameters and dimension-safe expressions
• materials and density expressions
• parts and fixed-placement nested assemblies
• named configurations
• instance suppression and part-material overrides
• deterministic BOMs
• geometric and physical mass properties
• canonical documents, migration, validation, and hashing
• design-impact and effective-feature hash reports

A numeric genus is exact for the backend representation. Unsupported results are explicit null; no backend or assembly path guesses, clamps, or silently converts the value.

​

Exchange

The bundled zero-override stock OCCT runtime additionally advertises single-solid deterministic STEP export protocol v1: identical bytes require the same backend shape representation, resolved metadata/options, implementation, and exact runtime artifact. Explicit wasm, moduleFactory, and attested runtimes retain weak raw STEP and omit this envelope until separately qualified. This is narrower than geometric canonicalization and does not make STEP a portable artifact or cache format. Exact aggregate body-set and assembly STEP remains unsupported. The unreleased public imported-body workflow admits exactly one committed solid through stock OCCT’s strong document-body import capability: This is a separate opaque one-body document and Evaluator.evaluateImportedBody(...) method. It verifies a caller-supplied SHA-256 and byte-length commitment before parsing, fixes healing to none, and does not publish the broader Document v7 product model. Multibody import, assembly import, repair/healing, automatic file/URL I/O, and approximate fallback remain unsupported.

​

Runtime coverage

​

Explicitly not in 0.1

• drawings, dimensions, PMI, and GD&T
• sheet metal and flat patterns
• assembly mates, joints, motion, interference, and contact
• CAM, toolpaths, posts, and stock simulation
• CAE/meshing/solver workflows
• general surfacing, NURBS editing, healing, and feature recognition
• variable fillets/chamfers and advanced shell modes
• complete transparent cross-run native shape caching

For the exact path-conditioning and topology-protocol boundaries behind this matrix, read the complete guide.