Opens in a new tab
Skip to main content
Lesson 07 of 10

Read the Result Like a Business Receipt

Match the agent’s completion claim to evidence of the actual requested result.

About 10 minutesNo coding experience neededExplore in your browser

Look around. Try a small click.

This lesson works as a written guide with interactive examples. You can explore here before opening the real application or provider dashboard. A recorded video has not been added yet.

Read the short lesson

What will make more sense

  • Match the agent’s completion claim to evidence of the actual requested result.
  • The evidence supports a local edit and does not establish publication.
  • The result describes a failed attempt to locate the target.

One idea to keep

Match the agent’s completion claim to evidence of the actual requested result.

The short lesson

Read the explanation at your pace

A completed action should leave a result you can understand. Think about paying a supplier: saying “I submitted it” is less useful than seeing the amount, supplier and confirmation. Agent work benefits from the same habit. Look for evidence that matches the job, and notice when a result only proves that an attempt was made.

Our result-receipts.md contains three fictional outcomes. The first says that the welcome note was read and includes the returned sentence. The second says an edit was applied and shows the revised sentence. The third says the tool could not find the target. Each result tells a different story. A friendly final explanation should accurately reflect that story rather than treating every attempt as success.

For a file edit, useful evidence might be the changed text and a comparison with the previous version. For a published web page, it might include both the saved source and the page people can actually open. For a message, it might include the intended recipient and the service's delivery or submission status. The right evidence depends on what was requested; a screenshot alone does not prove every background process worked.

Be precise about partial results. An assistant may create a draft successfully while the upload fails. It may save a change but be unable to check the public page. That work can still be useful. The final response should separate what is complete from what remains uncertain. You can then decide the next practical step without repeating completed work or assuming an unseen result.

In our simple example, you requested a one-sentence edit to a local welcome note. The matching receipt names that file, states the wording that changed and offers a before-and-after view. It does not claim the new sentence is already on the business website. Local source and public output are related, but publishing is a separate action that requires its own destination and evidence.

Use the activity to choose the most accurate completion statement. The illustrated comparison uses labels as well as red and green so the meaning does not depend on color. If you try optional practice, just open the prepared receipt and compare it with the note. You are learning a manageable review skill: connect the original request to an observable result and avoid filling in missing steps with assumptions.

Try it here

Try it here · no installation needed

Choose the next small step

Follow the prepared example, then select a response to see why it fits. Nothing is connected or changed.

This is a local learning example with prepared responses. It does not run VS Code or contact an AI service.

− Removed wording · before

Welcome to Cedar Street Repair. We are here to help with a wide variety of things.

+ Added wording · after

Welcome to Cedar Street Repair. Tell us what needs fixing, and we will explain the next step.

A note was edited locally, but no website was published. Which statement is accurate?

A prompt you can keep

These are example words to copy into your own AI chat when you want to try them. Copying does not send a request.

Read the prepared example for this lesson. Explain the proposed action, its target and the expected result. Keep this as an explanation; do not change files or connect accounts.

A tiny next step, if you want one

Optional: try 2 small actions at your own pace

You can finish this lesson by exploring the example above. These real-app actions are optional, and there is nothing to submit.

  1. Optional: open result-receipts.md and compare the three results.
  2. Optional: read welcome-note.md and check that its current wording matches the prepared “before” example.

A quick confidence check

These checkmarks are a personal reminder. Choose what feels familiar, and come back whenever you want.

Your place is saved in this browser when storage is available. There is no grading or account sync.

Try a short question

Choose an answer to see why it fits. You can try again or explore every explanation.

A note was edited locally, but no website was published. Which statement is accurate?

A tool reports that the file was not found. What does that establish?

If something looks different

My assistant or VS Code uses a different label.

Use the official help for your selected assistant and version. The course teaches the decision; the exact menu or capability can differ.

I do not have the account or feature used in the example.

Use the prepared browser example and downloaded notes. No account connection or paid service is required to complete this course.

Sources and further help

Read the official product guidance and related learning resources when you need them. You do not need to read every reference now.