Emergence CAD

BUILT ON EMERGENCE

One model. Every domain. Honest numbers.

The workspace takes cues from established tools in each field: SolidWorks’ feature tree, Altium’s routing, OpenROAD’s staged flow, Optiland’s ray analysis, OpenMDAO’s coupled solves and SolidCraft’s one-command-set design. The difference is the link between them: typed, unit-checked ports and one solver that iterates the loops between domains.

Use today

Flight sizing from measured bench tables or momentum theory; the ESC’s Rust electrothermal graph, heat sink and shop drawings; inverter losses and bus ripple from data sheets; feature-tree parts built and meshed by the Rust kernel; arm stress and modes against rotor excitation; surface-mount PCB placement, pours, obstacle-aware routing, kernel trace resistance, field-solved impedance, Gerber, Excellon and KiCad export; Verilog synthesis, equivalence, nine-corner timing, power and junction temperature, floorplan GDSII and Abbe lithography with inverse mask optimisation; sequential ray tracing of a Cooke triplet; a duct network’s operating point; a hangar’s heat balance on the BESTEST 600 envelope; PX4’s control cascade in a 6-DoF simulation; test plans that keep simulation, correlation and physical results apart. Every edit is a command, every domain is part of each revision, and the CLI and MCP server run the same registry.

Not yet

B-rep/STEP export and general sketch constraints; schematic capture and verified CAM output; PX4 software in the loop; PDK-backed layout, place and route and DRC/LVS sign-off; tolerancing, coatings and polychromatic optimisation; CFD of the fin channels’ turbulent regime; dynamic building simulation. Each studio lists the assumptions its answers inherit.

Fund the commons

Optional donations use the same development fund and donation flow as Fairground.