c_Learn & Practice AILEARN/Prove the work is done
← V2 video preview · three guided practices
V2 · REVIEW PREVIEW

Prove the work is done

Compare requirements, inspect changes, run real checks, and keep PASS, FAIL and NOT RUN separate.

Recording method: CLI file access was blocked. We attached real file contents to the prompt; Codex analyzed that supplied text. The recording tool then applied the reviewed one-line proposal and ran file, Git, Node and browser checks. This is an independent practice console, not the official Codex app UI. Processing waits are omitted. Voice is synthetic.

1080 × 1440 · 1:51English voice · EN / JA / VI captions

Choose your subtitle language in the player menu. Use fullscreen to inspect code; all explanations and practice prompts are also available in the localized lesson.

Translated transcript

0:00 · Evidence before acceptance

Done is a claim. Acceptance needs evidence. We will inspect the repaired practice folder, run the named checks, and test the page ourselves.

0:12 · Start from requirements

Read the requirements before judging the result. The heading must remain, the contact link must reach its section, and unrelated content must stay unchanged.

0:28 · Request a read-only review

This CLI session cannot access files. We attach the real requirements, diff, and independent check outputs. Ask Codex to assess this supplied evidence without claiming to run the checks itself.

0:43 · Read the limits

This is the actual review response. Read its limits as carefully as its successes. A command-line check cannot substitute for a browser check that never happened.

1:00 · Run independent checks

We independently run the syntax check and the practice verifier. Record the command and exit code for each. Five structural checks pass, but visual behavior still needs its own evidence.

1:18 · Add browser evidence

Add real browser evidence: click Contact, test the keyboard, and check a narrow viewport. These are desktop browser checks at a mobile size, not a test on a physical phone.

1:37 · Write the acceptance record

Record passed checks, failed checks, and anything not run. If a requirement lacks evidence, keep it open. Use the localized checklist to verify your own work next.

Recording evidence and limits

The evidence file contains the actual English prompt with supplied snapshots, Codex response, independent command outputs, file hashes and browser checks. It does not certify real-phone or Safari compatibility, fresh installation, or autonomous CLI file editing.

Download actual evidence · JSON
Esc · Close