Test, debug, and control the work.

Before you start

Use sourced evidence, explicit unknowns, and a controlled tool loop.

Each lesson follows the same rhythm: understand three small ideas, edit and run the code, then explain the result. Take one lesson at a time.

In your browser, JavaScript and local tools really execute against inspectable inputs. Model decisions and classroom records are authored examples. The optional SDK project runs separately on your computer with its own setup.

Your lesson sequence

1. 1Learn → build → reflectAsk before changing somethingApply least privilege and check explicit approval at the tool that would cause a side effect.
2. 2Learn → build → reflectTest behavior, not confidenceBuild representative and held-out cases; distinguish code checks, human review, and fallible model graders.
3. 3Learn → build → reflectFail clearly and recover carefullyClassify errors, bound retries, and distinguish a retryable read from a potentially duplicated write.
4. 4Learn → build → reflectSee where time and calls wentCompare correctness, duration, and call counts; use token and cost metrics only when a real runtime reports them.

CONNECT THE FOUR LESSONS

Your course checkpoint

Compare requests [A, A, C, A] with [A, C]. Keep the catalog unchanged and inspect the output and trace of each run.

• Explain why the output lengths differ while both need only two distinct reads.
• Show a changed proposal that requires a fresh review.
• Explain which failed status can be retried and where retries stop.

Use these lessons’ experiment inputs and lab notebooks to record your evidence. This is a self-review prompt; only the lesson questions and code cases contribute to the progress shown above.