How FEAI combines a language assistant with a rigorous solid-modeling kernel and deterministic finite element solvers — and where the line between them sits.
01/
The challenge
Language models are trained on text. They can describe finite element analysis fluently, but they cannot perform it — ask a chatbot to "run an FEA" and you get plausible-sounding numbers, not a simulation. The answer is not a smarter chatbot; it is putting the model in front of real engineering tools and constraining what it may do.
02/
The pipeline
Six stages, each deterministic and inspectable. The assistant only ever touches the second.
language01
A request in plain words, plus what is selected in the viewport.
feature actions02
The assistant answers with ordinary feature actions — extrude, revolve, fillet — not pixels or guesses.
B-rep kernel03
Actions run on a real solid-modeling kernel: exact boundary representation, booleans, fillets, mass properties.
mesh04
Tetrahedral or hexahedral finite elements generated from that geometry, with quality checks.
solver05
Deterministic finite element solvers compute stress, strain and displacement. No neural approximation stands in for the physics.
results06
Fields in the viewport; CSV and VTU exports for any other tool you trust.
03/
What the assistant does — and does not
It translates intent into parameters, chooses among the operations the engine actually exposes, and explains what it did. It does not compute physics, does not invent geometry outside the kernel, and does not bypass the feature tree: everything it creates is a normal feature you can inspect, edit and undo. The simulation math stays deterministic and verifiable.
04/
Grounding
The assistant can only emit actions the modeling engine implements. Unknown or ill-formed actions are rejected and reported, never silently accepted. There is no hidden computation between your request and the kernel — the action it emits is the action that runs.
05/
Validation
Every result can be taken elsewhere. Meshes, boundary conditions and material properties are exportable; results leave as CSV and VTU; whole projects travel as signed, encrypted .feai archives. If you want to check a number in commercial FEA software, you can.