FlyPython
Sign inStart a challenge

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

Define what a release record must prove

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

Command, exit code, parsed count and outcome, an unverified list, and a verdict that refuses zero-test projects.

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`.

Define what a release record must prove

Objective

Command, exit code, parsed count and outcome, an unverified list, and a verdict that refuses zero-test projects.

The lesson

Read TASK.md. The record is honest by construction: no-tests is its own verdict (never “passed”), and the unverified list ships with every record. Write the record fields your project needs — then trace each to its test.

Exercise

  • Draft the unverified list for a project you own
  • Ask: which field could a demo-minded agent fake? (exit codes alone — that is lesson 1 again)

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

Defining what a release record must prove before building it: command, exit code, parsed test count, outcome, an unverified list, and a verdict that refuses zero-test projects.

Hint 2 — Field by field

Take build_record's contract literally — all_passed is true only when every check has exit code 0 AND result 'ok'. Sketch the JSON on paper first.

Hint 3 — The unverified list

It is the honest core: a record that cannot say what it did not check is marketing, not evidence.

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 l02.
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 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":"verifying-ai-generated-code","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/verifying-ai-generated-code/files; you download nothing by hand. Prefer reading the source? Browse the folder on GitHub ↗