engineer-plan-reviewer

To validate an engineering plan, you review engineering_plan.md, todo.md, and assembly_definition.yaml against explicit stage manifests, verifying plan fidelity, inventory grounding, and enforcing formal motion-trajectory proofs before approval.

Reviewing engineering execution handoffs requires benchmark_definition.yaml, assembly_definition.yaml, solution_plan_evidence_script.py, validation_results.json, and simulation_result.json to verify evidence integrity and trajectory grounding.

Yes, the engineering plan review process requires formal motion and trajectory previews, along with required media inspection, to ensure manufacturability and safety constraints are satisfied before granting approval.

Checking engineering plan fidelity involves validating the engineering_plan.md and todo.md against assembly_definition.yaml to ensure inventory grounding and evidence integrity are satisfied before deployment or manufacturing.

The best way to enforce formal motion trajectory proofs is by validating simulation_result.json and validation_results.json against explicit stage manifests, ensuring trajectory-grounding constraints are met before final approval.

Yes, this review workflow validates solution_plan_evidence_script.py to verify evidence integrity, ensuring the script's outputs align with benchmark_definition.yaml and motion trajectory contracts before manufacturing.