FlyPython
Sign inStart a challenge

From “it runs” to “it ships”: verifying AI-generated code · Challenge 05 · 中文版

Gate your next release

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

Take the ship check to a project you own and make the record part of shipping.

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

Read https://flypython.com/skills/flypython/SKILL.md and start the FlyPython course `verifying-ai-generated-code`.

Gate your next release

Objective

Take the ship check to a project you own and make the record part of shipping.

The lesson

Add ship.json to one of your projects (command + unverified list), drop in ship_check.py, and run it. Wire the exit code into whatever gate you already have — CI, a release script, or a human checklist. From now on, “shipped” means a record exists and you have read its unverified list.

Exercise

  • Run the check from a clean checkout; the record must reproduce

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

Gating a release you own: wire the ship check into a real project and let the record be part of shipping.

Hint 2 — ship.json first

Give your project a ship.json with its real check command and an honest unverified list — the file is the contract, the script is just its executor.

Hint 3 — The honest record

Keep one SHIP-RECORD.json and note what it deliberately does not claim — a record that pretends completeness fails the course's point.

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 "From “it runs” to “it ships”: verifying AI-generated code" (course id course-verify-ship), checkpoint l05.
Machine-readable brief: https://flypython.com/api/challenges/verifying-ai-generated-code
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 l05, 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":"verifying-ai-generated-code","checkpoint":"l05","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/verifying-ai-generated-code/files; you download nothing by hand. Prefer reading the source? Browse the folder on GitHub ↗