Keep the source of truth outside the session
The workshop source note preserves three details outside any conversation: independent consultants, a two-hour planning session, and the confirmed-detail constraint.
The task definition, first brief, review finding, correction, and checkpoint remain separate artifacts. Together they preserve the job's history in ordinary files.
This synthetic example demonstrates a design choice. It supplies no evidence about migrations between named products.
Describe the job without provider vocabulary
The task asks for a concise workshop content brief using only the confirmed audience, offer, and constraint. Schedule and price remain unknown.
None of those requirements depends on a model brand. A later system can receive the same source and output boundary without inheriting hidden session context.
Make corrections portable
The draft introduces “Saturday sessions are available.” The finding names the source mismatch, and the corrected brief removes the sentence.
If only the final brief survives, the next system may repeat the same mistake. Preserving the correction teaches the job's boundary without relying on provider memory.
Export meaning with the artifact
The checkpoint carries the source identity, task purpose, finding, corrected result, and unresolved schedule and price. It omits private credentials and unnecessary system details.
The export proves that a reader can inspect the synthetic sequence. It does not prove that another product can import or execute it automatically.
Fit and poor fit
Replaceable model choice fits recurring work where source continuity matters more than one interface. It is less useful when the task is disposable and leaves no decision worth preserving.