Week 2 readings: context and tool contracts

Read the notes first. Before opening an explanation, predict which constraint each phase will preserve and which acceptance case should fail. After the studio, use the self-check to name the evidence you would rerun.

The only external readings below are pinned primary sources recorded in the course factsheets. Read the named sections at the cited revision; the factsheets are source records, not a substitute for the primary files.

Source 1 — Codex CLI instructions and plan schema (optional, 20 minutes)

Read the pinned base-instructions factsheet, especially its named primary-source sections “Task execution”, “Validating your work” and update_plan; follow its pinned source links. Then read the pinned plan-schema source named there. Scope: identify one instruction, one schema-enforced field and one rule whose enforcement the files do not establish. Record the pinned revision in your notes.

Source 2 — Qwen Code prompt builder and edit schema (optional, 20 minutes)

Read the pinned prompt-builder and tool-schema factsheet, then follow its named primary-source links for the prompt builder, edit and todo_write. Scope: compare a description-level request with a behavior checked by code, then write a call that should return a useful error. Do not infer behavior outside these files.

Source 3 — course contract (required, 10 minutes)

Read the Week 2 schedule, which is generated from SYLLABUS.md §4. Confirm the Week 2 topic, LO2/LO3 and the A2 and proposal due items. Scope: connect the studio record to the current course outputs.

Optional local inspection

The retained session recording and dissection are deterministic course material. From the repository root, use python lectures/week-02/session/show_session.py lectures/week-02/session/sample-session.jsonl to inspect request growth. This command reads the record and does not call a model.