Session 1. Configure the assistant and the repository instructions — Mon 14 Sep
Quick quiz (ungraded)
Q1: Which part of request → context → model → tool → verification does the model own?
You control the context, the tools, and the verification. The model fills one gap.
Correct. Same question, two answers. Everything around it is deterministic and yours.
Context is the policy file and the files you name. That is yours to write.
Q2: Why does this repository keep the policy in AGENTS.md and make CLAUDE.md point at it?
It reads whatever CLAUDE.md tells it to read. The pointer is a choice, not a limitation.
Correct. A rule that lives in three copies is three bugs waiting to disagree.
It is the longest of the three. Length is not the reason.
Q3: The assistant proposes a plan that edits tools.py, its test, and .github/workflows/pages.yml. What do you do?
Probably useful is not in the allowed set. A plan naming an unnamed file is already a rejection.
Correct. The allowed files were named in the plan step. Everything outside them is out of scope until you say otherwise.
The assistant does not grade its own work. You run the check; you read the verdict.
Q4: Where does an acceptance check for a code change live?
A summary is a claim. AGENTS.md says never claim a command ran unless it ran.
Correct. The command decides done, not the assistant's summary — here
uv run bootcamp check ch01. The assistant proposes, the command decides, you approve.A comment is not executed. The check has to run.
Q5: You gave the assistant "make search better" and it edited three files without asking. What is the homework?
A prompt is forgotten by Thursday. The fix has to survive the session.
Correct. Instructions are code; an observed failure is a bugfix to the instruction file.
The harness, not the model, made the difference. A different model with no boundary guesses the same way.