Turn one failed tool-using run into an inspectable trace, root cause, and regression case.
Scenario
An agent retries a write tool after a timeout and may duplicate an external side effect. The trace must show where the safety contract failed.
You will demonstrate
Project evidence
Each response is stored in this browser as you type. Include metrics, test output, or a decision rationale wherever the deliverable asks for it.
Record state, tool, validated arguments, outcome, retry decision, approval state, and terminal result for each step.
Required evidence: A compact trace plus root cause, correction, and regression assertion.
0/80 minimum characters
Runnable Python lab
Use an idempotency key to ensure a repeated request is not sent twice.
Project defense
Rate the evidence, not your effort: 0 missing, 1 weak, 2 adequate, 3 strong. All criteria must be reviewed, but a low honest score does not get hidden.
The trace makes the unsafe transition reproducible and ties the correction to a test.
Completion is controlled by stored evidence, deterministic tests, a decision defense, rubric review, and the artifact when required.
Optional cloud portfolio
An account is required. Submit only when the local completion gate passes. AI review is advisory and separate from deterministic completion.