Next Gen STEP AP242 Native-ish BREP Geometric Modeling Kernel
Aetheris 2.0.0-preview.2
Preview 2 is the feature-freeze release for Aetheris' current code-first CAD stack. It focuses on completing and reconciling existing work: Firmament V2, exact construction, engineering assemblies and modules, analysis, drawings, collaboration, packaging, and the advanced Forge extension boundary.
GitHub policy: although the version remains a SemVer preview, this is the current public Aetheris release and is intentionally marked Latest so the older PMI demo is not presented as the current product release.
Highlights
- Firmament V2 Concepts, Templates, Records, static Tables, typed values, semantic paths, Profile/Compose, and source-grounded diagnostics.
- Forge Host for ordinary application integration and KernelSDK for advanced
extension authors. Safe is the default; extensions declaring
UNSAFErequire explicitForgeHostOptions(AllowUnsafeExtensions: true)consent. - Exact ConstructionIR/BRep/AP242 workflows, bounded SurfaceMeshIR, Continuum dual representation, linear-elastic FEA, and tolerance stack-up.
- Firmament V2 assemblies with Interfaces, Mates, reusable definitions, AP242 product-structure round trips, and Cadmata assembly inspection.
- Built-in Surfacing, Panels, Piping, and engineering Modules with explicit bounded/experimental status.
- Drawing Templates producing SVG, vector PDF, and editable PPTX, plus DFM review and collaboration exports.
- Database-driven CAD sample using SQLite/LINQ and typed Forge Host invocation.
Install
The official Preview 2 paths are the NuGet global tool, the Windows x64 bundle (which includes Cadmata), and the Firmament VSIX from this release.
dotnet tool install --global Aetheris.CLI --version 2.0.0-preview.2
aetheris --version
aetheris --help
The CLI requires the .NET 10 runtime. The self-contained Windows bundle does not. Cadmata/browser and Vulkan/WebGL support are optional viewer concerns; no external STEP tool is required for compilation or inspection. The .NET 10 SDK, Node/tspack, VS Code packaging tools, and vendor CAD importers are development or interoperability tools, not CLI runtime prerequisites.
Application and extension developers can reference the version-aligned public libraries directly:
dotnet add package Aetheris.Kernel.Core --version 2.0.0-preview.2
dotnet add package Aetheris.Kernel.Firmament --version 2.0.0-preview.2
dotnet add package Aetheris.Forge.Host --version 2.0.0-preview.2
dotnet add package Aetheris.Forge.KernelSDK --version 2.0.0-preview.2
Breaking changes from Preview 1
.firmasmnow uses the Firmament V2 assembly profile. Historical JSON-shaped syntax is legacy and should be migrated toAssembly,Part,Interface, andMatedeclarations.Aetheris.Forge.Sdkwas split intoAetheris.Forge.Hostfor consumers andAetheris.Forge.KernelSDKfor extension development.- The generic
compose-operation-unresolved-profilediagnostic is nowConceptPathProfileNotAdmittedByCompose. - Template/static syntax follows current V2
Record,Static Table, and named argument rules; unsupported historical source forms are not silently guessed.
Known limitations
- Panel G1/G2 continuity, SheetMetal, SubD/SDF authoring, and general NURBS support are future work.
- SurfaceMeshIR, recognition/recovery, curved FEA, mixed-profile whole-loop fillets, and AP242 product structure are bounded as described in the feature manifest.
- Parasolid chamfer import behavior remains an external/vendor interoperability issue where Aetheris' AP242 output validates; geometry correctness is not weakened for an unverified importer workaround.
- Safe KernelSDK extensions receive only typed Aetheris interfaces by contract,
but .NET in-process code is not a cryptographic sandbox.
UNSAFEaccurately denotes arbitrary C# authority and requires explicit host opt-in.