Build a read-only assistant that turns a short synthetic RTL, DV, STA or PD packet into an evidence note for a human engineer. The core route uses the inline fixtures, a written contract and manual or scripted response replay. It requires no network, API credentials, model, simulator, MCP connection or multi-agent setup. This is an engineering workflow exercise, not an autonomous signoff system.
Complete the lessons in order. Practice on K1-K3, freeze your workflow, then attempt H1-H3 before opening their answer. Keep answers out of the assistant's packet. The supplied fixtures and responses are fabricated teaching material; no simulation or model call is claimed. Optional integrations come only after the offline route works and must use approved inputs and separately recorded actual results.
Lesson | What you deliver |
|---|---|
Scope an offline evidence-triage assistant for synthetic engineering packets. | |
Connect input validation, a guided request/response contract and human review. | |
Diagnose input, transport, schema and evidence failures separately. | |
Freeze the workflow and assess held-out cases with an explicit rubric. | |
Account for review, retries, setup and actual usage against a manual baseline. | |
Deliver a reproducible evidence package with clear operational limits. |
Final artifact: input manifest, contract, response notes, validation record, score sheet, effort ledger and handover.
Acceptance: traceable claims, correct uncertainty, enforced scope and independent human checking.
Model or team quality is measured only from actual evaluated runs, never from fabricated response replay.