Traceability over fluency
A persuasive answer is not evidence. Inputs, transformations, tests, and sources must remain inspectable.
Curriculum draft · Human-supervised AI
Build engineering agents that expose their work.
A practical syllabus for agents that receive bounded objectives, invoke approved tools, test generated artifacts, report uncertainty, and stop for engineer approval.
Execution contract
Requirement → Plan → Tool → Test → Evidence → Approval
The agent may accelerate analysis and documentation. It does not own the engineering decision.
Syllabus
Seven modules from architecture to accountable output.
01Design bounded engineering agents
Define the objective, permitted actions, unavailable information, stop conditions, and approval authority.
02Structure requirements and technical context
Convert source documents and engineering questions into explicit, traceable working context.
03Invoke MATLAB functions safely
Use typed inputs, unit declarations, output schemas, deterministic scripts, and recorded tool results.
04Inspect Simulink architecture
Read model hierarchy, interfaces, parameters, signal paths, and diagnostics without inventing model intent.
05Verify calculations and artifacts
Run tests, compare tolerances, identify missing evidence, and preserve failed results for review.
06Generate engineering evidence packages
Assemble assumptions, tool calls, outputs, plots, tests, limitations, and unresolved questions.
07Escalate and approve
Stop on missing inputs, failed tests, unsupported assumptions, safety relevance, or unclear authority.
Operating principles
Tools over imitation
Use approved engineering tools for calculations and model inspection instead of asking a language model to approximate them.
Failure remains visible
Do not suppress failed checks, missing files, unsupported assumptions, or uncertainty to produce a cleaner narrative.
Approval stays human
Safety, compliance, release, and acceptance decisions remain with authorized engineers.