Interactive example · from Start here: Verify the result

The completion report

you

You said the mobile menu fix is done. Before I look: how do we know?

Which completion report gives you evidence rather than confidence?

A“Done. The implementation is robust and production-ready.”

you

Which check did you actually run?

agent

I reviewed the code carefully. It follows solid patterns.

you

So nothing ran. On my phone the menu still overlaps the logo.

not yet

Confidence adjectives are not checks. Nothing here tells you what ran or what you can inspect. AF-04

B“The focused navigation check passes, the full build passes, and the diff contains two files. I could not test VoiceOver.”

you

Show me.

agent

Here is the build output, the focused check that fails if the links overflow, and the two-file diff. The VoiceOver pass I couldn’t run in this environment, so that gap is yours to accept or to test.

you

I can tap through each claim. The one thing not checked is labeled, not hidden.

good call

You get named checks, a bounded change surface, and an explicit limitation. Each claim can be inspected.

C“All tests pass, so the requested behavior is correct.”

you

Which of those tests fails if the menu overflows?

agent

None. No existing test covers the menu.

you

So the suite was green before the bug and green after. It never saw the thing we changed.

close, but

Passing tests matter only if they cover the requested behavior. Ask which test was capable of failing for this change. AF-05

← Back to the lesson · raw data