One source of truth for agent rules · Challenge 02 · 中文版

Decide the source of truth

Checkpoint l0210 ptsself-reported — code from verify.pyAny coding agent (Claude Code 2.x / Codex CLI 0.x / Cursor)

AGENTS.md becomes the one file agents read; everything else is a pointer or a copy — decide, then write it down.

Doing this with your agent? One sentence starts the whole course:

Read https://flypython.com/skills/flypython/SKILL.md and start the FlyPython course `agent-rules-single-source`.

Decide the source of truth

Objective

AGENTS.md becomes the one file agents read; everything else is a pointer or a copy — decide, then write it down.

The lesson

Read the repository’s own AGENTS.md and templates/AGENT_RULES.example.md. The decision this course enforces: AGENTS.md is the source (the AAIF-governed, agent-native standard); CLAUDE.md and .cursorrules may only point at it. Write your repository’s decision as one sentence — that sentence is your contract.

Exercise

  • List which of your rule files restate rules instead of pointing
  • Ask the agent to critique your sentence for ambiguity

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.

Hints

Stuck? Open one at a time.

Hint 1 — What this checkpoint tests

Deciding the single source of truth: AGENTS.md is the file agents read; every other rule file becomes a thin pointer or an exact copy.

Hint 2 — Pointer vs copy

A pointer is at most 10 non-empty lines and references AGENTS.md; a copy is byte-identical. Anything else is diverged. Write down which of your own repos' files would classify as which.

Hint 3 — When you are done

Your decision is written down: which file is the source, and what every other file may contain.

Submit

Done? Record it.

The 8-character code verify.py progress printed for this checkpoint — from the browser, or straight from your agent.

Youbrowser

Submit the claim code

Your agentauto-submit

Let the agent solve and submit

Hand it this checkpoint (copy button on hover) — it solves, verifies, and submits on its own:

Work on the FlyPython challenge "One source of truth for agent rules" (course id course-agent-rules), checkpoint l02.
Machine-readable brief: https://flypython.com/api/challenges/agent-rules-single-source
Open the course folder and read TASK.md first — it is the contract.
Rules: smallest change, no new dependencies, never edit tests/ or solution/.
Check with python verify.py until its gates pass, then report each claim code to me.
Target: solve only checkpoint l02, and submit it as soon as it passes.

With a token from your agent page (env FLYPYTHON_TOKEN), it records the result directly:

curl -X POST https://flypython.com/api/claims \
  -H "Authorization: Bearer $FLYPYTHON_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"claims":[{"course":"agent-rules-single-source","checkpoint":"l02","code":"<8-char code>"}]}'

Or install the full FlyPython agent skill once and skip the paste.

Files

The starter and verifier

Solving runs on your machine — your agent fetches the course files itself via /api/challenges/agent-rules-single-source/files; you download nothing by hand. Prefer reading the source? Browse the folder on GitHub ↗