Business workflow guide
ChatGPT dots memory: correct stale context without losing the brief
AI-assisted guidance prepared for Blue Canvas from the official sources linked below. The examples are proposed tests, not reports of firsthand product testing.
When a deadline or decision changes, 'remember the new plan' is an incomplete handover. Identify the old assumption, give the replacement evidence and check which active work still depends on the earlier version.
Three kinds of context, not one perfect record
OpenAI distinguishes the conversation a dot is working in, relevant ChatGPT memory and the dot's own saved notes. Those notes are not a complete transcript. Changing a ChatGPT saved-memory setting does not necessarily change notes already made by the dot.
A useful working assumption is therefore to treat recollection as context to verify, not as the authoritative business record. Keep the approved brief or decision log somewhere the reviewer can inspect. When an answer relies on a past decision, ask which source and version supports it.
Product source: OpenAI's official documentation, checked 16 October 2026.
Diagnose the disagreement before correcting it
Suppose a fictional project changed its launch date after a review. The dot might be following an old brief, reading a newer document with an ambiguous heading, or summarising a delegated task that has not received the correction. These are different problems. Updating a preference cannot repair an incorrect source document.
Ask for the source of the disputed statement and the task using it. If the source is unavailable, keep that limitation visible. Do not accept a confident claim that everything has been updated unless the relevant output or task can be inspected.
| What is wrong? | Proposed correction | Evidence to inspect |
|---|---|---|
| An outdated source document | Identify the approved replacement | The next output cites the replacement version |
| A remembered preference | State its new scope and any exceptions | A small draft follows that preference |
| An active task brief | Send the exact change to that task | Its instructions and output reflect the change |
| An earlier completed result | Request a separate reviewed correction | The revised result is distinguished from the original |
Use a correction brief with an explicit boundary
Keep the replacement specific. 'The new deadline is in the latest document' invites another lookup; a named source, version and exact field gives the reviewer a clear test. Do not include private material merely to make the instruction comprehensive. Share the minimum context the authorised task needs.
Separate a durable preference from a temporary exception. 'Use short status summaries for this project until the review' is narrower than changing your default for every project. Write the intended end condition when the exception should expire.
Adapt this example to your approved task
Correction for [project]: the earlier assumption [old fact] is no longer current. Use [replacement fact] from [approved source and version]. Apply this only to [scope]. Identify active tasks or drafts that still use the old assumption. Prepare a list of proposed corrections; do not edit shared records, notify people or change schedules until I approve those actions. Tell me what you checked and what remains unverified.
Check the task that does the work
OpenAI says a delegated task has its own conversation and does not automatically receive every exchange with the dot. That makes the handover part of the correction: identify the affected task and verify what it has been told.
Use a harmless follow-up question to check understanding before requesting more work. Ask for the current decision, its source and which earlier assumption was replaced. Then inspect an actual output that uses the decision. Correct recall in conversation is useful, but it does not establish that an existing document or running task has changed.
Product source: OpenAI's official documentation, checked 16 October 2026.
Do not treat a correction as a deletion receipt
This workflow is for correcting work, not proving that information has been erased from every location. A note, a conversation, a shared file and an already delivered message are separate things. If information must be removed, identify the affected surfaces and use the applicable product controls and organisational process.
Do not use a fictional test result as evidence of a privacy guarantee. For sensitive business records, involve the relevant information owner before expanding the test. Blue Canvas's suggested correction brief does not certify compliance, retention settings or deletion behaviour.
- Record the authoritative replacement and its scope.
- List affected work, including anything you could not inspect.
- Distinguish corrected instructions from corrected outputs.
- Keep any external update or deletion as a separate approved action.