Next Gen STEP AP242 Native-ish BREP Geometric Modeling Kernel
CLI reference
Primary public commands:
Commands use aetheris unless a separate executable is shown. The optional aetheris-3dm tool includes native Rhino3dm; installation and source usage.
| Command | Purpose |
|---|---|
validate <file> [--json] |
Check admission; generic mechanical validation includes in-memory geometry preflight |
frontend-shadow <file> [--json] [--ast] [--validate] [--benchmark] |
Developer-only original-source structural evidence and bounded production comparison |
build <file> [--output path] [--json] |
Materialize and export exact STEP AP242 |
inspect <firmament-or-step> [--json] |
Inspect source semantics or route STEP to analysis |
aetheris-3dm inspect <file.3dm> [--json] |
Inventory Rhino/OpenNURBS metadata, units, BRep topology, and unsupported objects |
aetheris-3dm recover <file.3dm> [--body N [--edge N|--face N]] [--json] |
Measure provisional analytic/non-rational recovery candidates; see 3DM recovery evidence |
analyze <step> [--json] |
Reinspect topology, surfaces, bounds, manifold state, and PMI |
analyze section <step> ((--xy|--xz|--yz) --offset value|--origin x,y,z --normal x,y,z) [--out section.svg] [--json] |
Extract trim-aware analytic section loops in a principal or arbitrary plane and optionally render deterministic SVG evidence |
analyze compound <step> [--json] |
Inspect every disconnected rigid root without silently selecting or merging one |
analyze compare <reference.step> <candidate.step> [--shape [--shape-resolution N]] [--json] |
Compare two parts: bounds, counts and surface families; with --shape, also which analytic surfaces each side lacks and where material differs |
view <file> |
Open in bundled Cadmata |
fea <file> --out-dir dir [--json] |
Compile and solve the bounded linear-elastic analysis |
sheetmetal ... |
Inspect, recognize, recover, compare, or flatten Sheet Metal |
sculpture build <source> ... |
Build the bounded non-manufacturing Sol 1 AP242 artwork, evidence, and SVG preview |
section-chain <build|inspect|validate> <file.firmament|flagship|twist|two-profile> ... |
Lower authored SectionChain, Loft, or Loft<Hollow> into SectionChain IR and report frames, spans, correspondence, pcurves, conservative intersection qualification, STEP, and reimport evidence |
wireframe <model.step> [--out preview.svg] [--view iso|front|top|right] [--density N] [--json] |
Render deterministic exact-edge and trim-clipped surface-isoline SVG evidence |
asm ... |
Inspect/execute/import/export assemblies |
Generic mechanical validate now runs the existing engineering compilation in memory, including selection binding, capability checks and geometry/STEP preflight. It writes no output file. Its report includes validationLevel (Built, BuildRejected, or ParsedNotBuilt) and developer-only parserRoute metadata. --explain prints the route, admission level and available instance counts. --parse-only explicitly requests static analysis and reports parsed-not-built on success. Drawing, Analysis, PlasticShell, Sculpting, Plateau and Piping currently lack that separate static admission path: they reject this option with firmament-validation-option-unsupported and NotValidated, rather than silently materializing geometry. Structural and Garment reuse their existing static analyzers. External --forge-pack validation is also labelled parsed-not-built: those descriptor providers are not installed into normal build. Domain-specific validators retain their separate scope; inspect their reports. This is not a promise that unchanged source can never encounter a later environment or kernel failure.
Mechanical Model and material-bearing Struct documents now use the unified lexer/AST admission path (UnifiedMechanical). The ignored Compose Fillet, erased Rect2 field and unused Slot2 route-perturbation cases are repaired. Profile/Compose build execution consumes admitted engineering inputs. Other dedicated domains retain their existing owners; see the production migration qualification for its scope and evidence.
validate file.firmament --shadow --explain --json opts into the developer
envelope: shadow contains original-source syntax status, AST summary, original
diagnostics and a bounded comparison against the generic production projection;
productionValidation contains the ordinary validation command's unchanged
report. Parsed means StructuralOnlyUnbound, not engineering validity. The
comparison explicitly reports unqualified declarations and fields. --ast adds
the detailed source tree and trivia only when requested. frontend-shadow
without --validate collects syntax/projection evidence without geometry.
frontend-shadow --corpus fixtures writes JSON and Markdown under ignored
artifacts/local/frontend-x1/corpus by default. It includes invalid, legacy and
speculative sources; exit zero means collection completed, while qualified: false remains explicit. Per-file exit one means structural rejection or, with
--validate, production rejection. Normal mechanical compilation uses the same syntax parser through its production
AST binder; the developer comparison does not control admission. --benchmark measures twenty warm structural parses and current
thread allocations, excluding file IO, production parsing, comparison and geometry.
Run aetheris <command> --help for exact options. JSON is a public automation surface, but its root is command-specific: process exit status is authoritative, validate reports firmamentV2Validation.status, and materializing/analysis commands report success where documented. Diagnostics are structured; artifact paths are explicit; wireframe reports trim/pcurve coverage and a deterministic SVG hash; Sheet Metal reports regions, bends, and lowered features separately; FEA reports requested/result artifacts; sculpting builds report every BodyState, GeometricDelta, validation evidence, surface-family inventory, and the sibling .delta.json path; other builds report emitted features and PMI export evidence. Counts describe semantic items at the stated layer, not arbitrary STEP entity counts.
Generic STEP analysis reports analytic placement and size information where it is present: planes include origin and normal; bounded cylinders and cones include axis, axial extent, and circular-boundary angular extent; spheres include center and radius; and circles include center, axis, radius, sweep, orientation, and their actual trimmed endpoints. Circular-edge bounds and section output are computed from those trims rather than from the supporting full circle. analyze section returns normalized closed loops with deterministic orientation and nesting metadata; --out is intended as compact geometry evidence, not a substitute for the JSON record.
analyze compare --shape is for checking a reconstruction against an original. Faces are grouped by their analytic surface (plane normal and offset, cylinder axis and radius, cone apex and half-angle, sphere, torus), so a candidate that splits or merges faces differently still matches. The report lists each surface the candidate is missing and each one it adds, with the original's face ids and bounds. For example, a missing cylinder r=10 axis=(0, 1, 0) through (30, 0, -25) is a horizontal hole the candidate does not have. Material is compared by casting parallel Z rays through both tessellations on a grid (--shape-resolution cells along the longer side, default 400). The report gives each side's volume, the volume only the reference has and the volume only the candidate has, intersection over union, and the connected regions of difference with their bounds. These volumes are approximate to the display tessellation. Single-cell slivers along curved walls, where the two tessellations' chords disagree, are counted but not listed. Spline surfaces are compared by count only.
Part mesh exports
aetheris mesh part.step --format stl --output artifacts/local/part.stl --json
STL export checks paired opposite-direction edge uses, connectedness, nondegenerate triangles and positive signed volume. It repeats those checks after converting to STL's float32 coordinates and merging equal stored positions. Precision collapse rejects before replacing the destination file. Build nearer the coordinate origin or use a representation retaining greater coordinate precision if float32 cannot preserve the part's detail.
JSON includes orientationConflictEdgeCount, consistentlyOriented,
outwardOriented and meshSignedVolumeMm3. The volume describes the stored
triangle approximation, not the exact engineering part. maxChordalDeviation
describes shared boundary sampling; it is not a bound on volume error. watertight reports the
mesh checks above; it does not prove freedom from self-intersection or fidelity
to a nominal design. OBJ reports the same directed-edge diagnostics while
retaining the structured polygon representation.
Assembly display meshes
For a standalone BRep part, use
aetheris mesh part.firmament --format display-json --output artifacts/local/part.display.json --step-output artifacts/local/part.step --json.
This exports the shared display schema in millimetres with one definition and
one identity-frame occurrence. The optional --step-output writes the exact
body from the same compilation. Compilation and tessellation finish before
either output is written; filesystem write errors may still leave one output.
This is the transport used by Aetheris CAD for Blender.
aetheris mesh <assembly.firmament|assembly.firmasm> --format assembly-json --output <file.mesh.json> --json exports shared local definition meshes and stable world-space occurrences. Failed geometry is not omitted. The default destination is artifacts/local/mesh/<name>.mesh.json. See editable mechanisms for the schema and a working consumer.
Generate engineering drawings
aetheris drawing generate <part.firmament|model.step> --out-dir <directory> --json creates PDF, SVG, editable PPTX, Drawing IR and validation evidence. The default automatic path requires a complete nominal dimension plan; currently rectangular plates/boxes with disjoint Z-through holes are qualified. --linear-tolerance, --angular-tolerance and --material are explicit drawing requirements. --reference-only emits clearly incomplete visualization. See drawing generation for admission, reconstruction qualification and manufacturing limits. Use drawing compile for authored drawings and assembly BOMs.