Artificial Intelligence

Text briefing | Sources checked October 30, 2026

How to Update an AI Draft After a Human Decision

Revise one affected line after a verified decision, with a source map and human review.

For
Anyone updating a public note or flyer from a verified, non-sensitive source.
Use it to
Change only what the new decision supports and preserve what remains unknown.
Update one line after a decision: source, change, check

Yesterday's draft may be accurate about yesterday's uncertainty and wrong about today's decision. When a responsible person supplies a new answer, ask AI for a small, traceable revision. Then check the new wording against the new source before sharing it.

For: Anyone updating a public note, flyer, email draft, or status message from a verified, non-sensitive source.

Use it to: Change only what a new decision supports, retain what remains true, and leave other unknowns open.

One entirely fictional update

This neighborhood puzzle swap, its people, note, decision record, and draft flyer are constructed teaching examples. No real person answered a question, no message was sent, and the sample AI response below is illustrative rather than an observed separate model run.

The earlier fictional note says:

Line 1. A neighborhood puzzle swap is planned for Saturday, November 7, 2026, from 10 a.m. to noon. The library lobby reservation is confirmed.

Line 2. Flyer copy is due Thursday, November 5, at noon.

Line 3. Sign-up wording is undecided. Maya is the decision owner; no answer is recorded in this version.

Line 4. Leo offered to bring boxes. The number of boxes is unknown.

The draft flyer appropriately holds the sign-up line: “Sign-up details to be confirmed.” It should not say “No sign-up required” yet. That was the point of the previous lesson: ask Maya a neutral question rather than having AI decide for her.

Now add a new fictional record, clearly separated from the old note:

Line 5 — new decision record, Friday, October 30, 2026, 9 a.m. For this puzzle swap, Maya approves the flyer wording: “No sign-up required. Drop in between 10 a.m. and noon.” This record is part of the constructed example, not a message from a real Maya.

A non-AI calendar check confirms October 30 is Friday, November 5 is Thursday, and November 7 is Saturday in 2026. In real work, verify that the new record actually came from the person authorized to decide, is current, and applies to this particular event. A forwarded, partial, or ambiguous message is not enough merely because it sounds decisive.

Ask for a bounded revision

Give AI the old source, the new decision record, and the current draft as separate blocks. Ask it to revise only the affected line and show its work. Use only material you are authorized to share with that AI service.

Task: Update only the sign-up sentence in the draft flyer below. Treat the numbered note as the earlier version and line 5 as a later decision record. Do not pretend line 5 was known when the earlier note was written. Return: (1) the exact sentence to replace, (2) one proposed replacement, (3) source lines supporting every claim in the replacement, (4) facts that should stay unchanged, and (5) anything still unknown. Do not add details, send the flyer, or declare it approved. If the new decision record's owner, scope, or wording cannot be verified, say “hold for human review” instead of producing a publish-ready line.

Earlier note: [paste lines 1–4 from an approved, non-sensitive source]

New record: [paste line 5 with its verified source and time]

Current draft: [paste the draft flyer]

OpenAI's current prompt guidance recommends clear, specific instructions and enough context; it also describes reviewing and refining a response. That supports the prompt's structure. It does not prove the model will make the right edit.

What a checked illustrative output looks like

An illustrative response for the fictional record could be:

PartExample
Replace“Sign-up details to be confirmed.”
Proposed line“No sign-up required. Drop in Saturday, November 7, between 10 a.m. and noon.”
SupportLine 5 supplies Maya's decision and drop-in wording; line 1 supplies Saturday, November 7 and the event hours.
KeepThe event date and time in line 1 and the flyer deadline in line 2 have not changed.
Still unknownLine 4 does not say how many boxes Leo will bring.

The new record now supports “No sign-up required,” but it does not rewrite history. The earlier line 3 truthfully recorded an undecided status at that time. The replacement may be used only after a person checks line 5's authority and scope, confirms the phrasing, and approves the final flyer. Do not present this table as a result measured from a separate AI run.

Five checks before you publish the revision

  1. Provenance: Who made the new decision, when, and for which event? In the example, line 5 identifies Maya, time, and this puzzle swap. In real work, verify the original record, not merely an AI summary.
  2. Scope: Did the answer settle only sign-ups or also boxes? Here it settles sign-ups only. The box count stays unknown.
  3. Exact change: Compare the old draft and proposed replacement word by word. “No sign-up required” and the drop-in time are supported by line 5; the date comes from line 1. Do not add “free,” “unlimited,” or a box promise.
  4. Unchanged facts: Recheck dates, hours, place, and deadline against the current source. A model can change unrelated details while polishing a sentence.
  5. Human approval: Show the changed line and its source to the responsible person. The AI draft is not approval, and a recorded decision is not permission to publish an unreviewed public artifact.

OpenAI's accuracy guidance warns that a confident response can be wrong and recommends checking important details against reliable sources. NIST's AI Risk Management Framework 1.0 discusses objective evidence, transparency, and human oversight in the broader context of trustworthy AI. The five checks above are Short Briefing's practical application of those ideas, not a tested guarantee or a requirement stated verbatim by either source.

Try one safe update

Use a harmless, current note that you are authorized to put into an AI tool. Add one verified new fact or decision, then ask for a one-line change, a source-line map, and a still-unknown list. Compare the proposed line with both versions yourself. If the new source is unclear, keep the draft on hold and ask a human.

Sources checked October 30, 2026: OpenAI, “Prompt engineering best practices for ChatGPT” (page displayed “Updated: 11 days ago”); OpenAI, “Does ChatGPT tell the truth?” (page displayed “Updated: 7 days ago”); NIST, AI RMF 1.0, section 3 (2023 excerpt; revision in progress). The sources support the general checking approach, not the fictional event, an observed AI result, or a measured improvement.

Disclosure: AI assisted this lesson's research and drafting. Short Briefing constructed and checked the fictional example, prompt, and illustrative output. No real decision, message, external AI test, performance gain, or subscriber outcome is claimed. Any companion video uses synthetic narration and original project graphics.

One step you can use

Revise one line, then check it.

Ask for the changed sentence, its source map, and what remains unknown. Have the responsible person review the final artifact.

Limits

A well-formed revision can still rely on a forged, stale, or incomplete new record. Verify the source and scope yourself.

Disclosures

AI assisted research and drafting. This puzzle swap, decision, prompt, and illustrative replacement are fictional. No real message, separate AI test, measured gain, or subscriber outcome is claimed. Any companion video uses synthetic narration and original project graphics.

Corrections

No corrections have been recorded. See the corrections process.