Model ingestion
Structured interchange and validated import/export for supported formats.
Developers / Engineering platform
Build on
clear contracts.
A disciplined future developer surface for model definitions, scenarios, engine adapters and evidence. Public SDK maturity and desktop integration have not yet been verified.
01 / Integration philosophy
Typed boundaries.
Reproducible inputs.
Engineering systems need explicit units, IDs, revisions, assumptions and run provenance. The intended extension architecture favors structured contracts over hidden runtime behavior.
Developer availability: Internal repository source and historical service endpoints do not constitute a stable public API or released SDK. No credentials, internal URLs or private implementation files are published here.
- Declare versioned model and component specifications.
- Describe units, coordinate systems and physical assumptions explicitly.
- Validate imported definitions and resources before execution.
- Integrate solvers behind tested adapters rather than assuming universal compatibility.
- Produce results with manifests, traces and reproducibility metadata.
02 / Future developer surface
Extension areas.
Engine integration
Versioned adapter interfaces with tested solver prerequisites and limitations.
Evidence pipelines
Immutable or versioned run metadata, diagnostics, trace records and exports.
03 / Availability
Developer access is not yet public.
Official SDK downloads, API version contracts, examples and compatibility guarantees will appear only after independent implementation and release checks.
Understand the architecture