Checklist

Check what the AI actually changed

A convincing sentence is not the same as a changed system.

About 1 min read

Before you use it

Use when
  • An assistant says it sent a message, changed a file or merged an update.

Keep this limit in mind

  • Completion does not prove permission or quality. Respect access limits; a screenshot can show an older state.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Checklist

  • Check the intended recipient, file or record, then its current status or revision. For a batch, check which items succeeded and which failed.
  • If the result is missing, inaccessible or still pending, report that state. Check for an existing action before retrying a send or another action that could be duplicated.

Why it matters

Before the action, name the result you expect and where you will check it. Afterwards, open that service and match the target, action and result to your request. A link or identifier helps locate the result; it does not replace checking it. Keep a prepared draft separate from a completed action.

An example

An assistant says an issue was closed. Open the intended project and issue: closing a different issue does not fulfil the request.

Check your result

The observed result matches the requested target and action. Unchecked items remain unverified; pending items remain pending.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingCheck what the AI actually changed

Evidence and sources
Supports

NIST says AI trustworthiness results should reflect relevant actors' input about performance in deployment contexts and be documented.

Claim limit: NIST provides a general organisational evaluation/documentation framework, not this consumer receipt-checking procedure or evidence of its effectiveness. Matching targets, handling partial/pending results and checking before retry are editorial advice; observation does not establish authorisation or quality. Source reading history: selected_passages; 2026-10-10; NIST AI 600-1, printed p. 39 (PDF p. 43), MEASURE 4.2 heading. The cited official page was retrieved on 2026-10-10 and the named passages were inspected. Card-specific adaptations are independent editorial reasoning, not validated improvements. MEASURE 4.2 heading reread in the linked report on 2026-10-12; it supports the general framework statement, not the card-specific action receipt procedure. Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review.

NIST AI RMF Generative AI Profile · MEASURE 4.2: deployment-context trustworthiness results, relevant actor input and documentation

All sources (1)
Edition and review

Version 0.1.0 · Published

Edition checked · 2026-11-13

Read this idea as JSON · Release details