Skip to content

Latest commit

 

History

History
49 lines (36 loc) · 1.9 KB

L01.md

File metadata and controls

49 lines (36 loc) · 1.9 KB
id course-agent-rules-l01
type course
title Measure the drift you already have
summary Run the checker against the three scenario repositories and read drift as a test failure, not a vibe.
lang en-US
content_version 1
status reviewed
reviewed_on 2026-09-12
hints
title body
What this checkpoint tests
That you can measure drift instead of feeling it: run the checker on the three scenario repositories and read each result as a test failure, not a vibe.
title body
Find the three repo states
The scenario folders show the three shapes the contract classifies — a clean single-source repo, one with a thin pointer, and one where a copy has drifted. Name which is which before moving on.
title body
When you are done
You can explain what `ok=false` means in terms of files, not feelings: which file diverged from `AGENTS.md` and how the checker knew.

Measure the drift you already have

Objective

Run the checker against the three scenario repositories and read drift as a test failure, not a vibe.

The lesson

Run python starter/rules_check.py scenario/drifted — it says everything is fine. That is the bug: three files disagree about one behavior and nothing notices. Then run the verifier:

python verify.py starter --expect-failure

Exercise

  • Map each verify.py --expect-failure name to a real drift class: no source, no pointer detection, no drift reporting
  • Open scenario/drifted/.cursorrules and find the rules that contradict AGENTS.md

Checkpoint

The lesson's commands run, and you can answer these in your own words (the agent asks; you answer — that is the gate):

  1. Which command did this lesson run, and what did it decide?
  2. What failed at the start, and why — in your own words?
  3. Before trusting a similar change next time, what would you check first?

Expected evidence

The command transcript and your answers.