engineer-coder

Automating engineering handoffs involves translating approved plans into an executable solution_script.py with validated revisions. The process preserves engineering_plan.md contracts while applying bounded retries, pattern selection, and simulation.

Generating render-bundle evidence for CAD simulations requires querying frame-indexed objects.parquet data. This satisfies strict contract requirements and grounds results in engineering_plan.md anchors.

Plan_refusal handling works by generating a refusal plan via plan_refusal.md when an engineering task is infeasible. It enforces strict evidence and contract requirements to reject handoffs that cannot be executed.

You need an approved engineering_plan.md file to start automating CAD solutions. This document provides the necessary contracts and anchors required to generate the solution_script.py and validation evidence.

You can apply bounded retries and mechanism-pattern selection to engineering validation tasks. The automation supports these mechanisms alongside simulation and render-evidence inspection to ensure robust solution revisions.

Engineering plan grounding requires strict evidence and contract requirements to ensure reproducible, contract-grounded implementations. This prevents unverified handoffs from producing invalid solution_script.py outputs or incomplete validation data.