FEA Feedback Loop

The FEA feedback loop is an engineering agent pattern in which a model generates CAD code and a deterministic controller validates the resulting artifact against physical requirements using finite element analysis (FEA). When the artifact fails, the controller produces typed feedback that the model uses to repair the design. The loop repeats until all requirements pass or a budget limit is reached.

Why this pattern matters

Visual plausibility is not engineering validity. A part can look correct in a rendered image while violating stress limits, displacement thresholds, clearances, or assembly constraints. The FEA feedback loop is the technical solution: replace human intuition checks with deterministic measurement.

Key result from Hephaestus-CCX benchmark: One FEA feedback round improved mean requirement pass rate by 13.4 percentage points on average. In the strongest reported run (GPT-5.5/high), mean pass rose from 38.8% to 60.5%, yielding 9 strict passes out of 50 cases. These results are meaningful but still far from autonomous production readiness.

System architecture

Engineering Brief
   → Typed Blueprint (requirements decomposed into measurable contracts)
   → CadQuery Program (parametric CAD code generated by the model)
   → STEP Artifact (exported 3D geometry)
   → [Deterministic Controller]:
       - Geometry checks
       - Rich-view rendering (multi-angle inspection images)
       - FEA simulation (stress, displacement, buckling, modal)
       - Requirement verdict (pass / fail per check)
       - Typed feedback (failure type, measured value, threshold, selector)
   → Repair Decision (model modifies blueprint or code)
   → (back to CadQuery Program)

Roles: model vs. controller

Responsibility	Owner
Design intent, blueprint, CAD code	Model
Execution, measurement, FEA, feedback	Deterministic controller
Artifact versioning, audit log	Engineering record
Final approval for high-consequence parts	Human engineer

The controller is the governance layer, not plumbing. It is what makes the agent’s output trustworthy enough to inspect.

Production boundary

This pattern is not production certification. Generated artifacts still require independent review before use in safety-critical, regulated, or manufactured designs. The loop is a powerful assistance tool, not an autonomous sign-off mechanism.

Before deploying: validate solver configuration, meshing stability, unit discipline, material properties, and the human approval boundary.

Related

• BoundedAgent — the broader pattern of which FEA feedback is a domain-specific instance
• AgenticGovernance — audit and approval principles that apply to engineering agents
• CadQuery — the parametric CAD scripting tool used by the generating agent
• ManufacturingAIAdoption — where this pattern sits in the manufacturing AI adoption ladder