Extract the Final Prompt From a Chat — Bottle the Declared Version
When the chat says "this is the final version", that's the moment to bottle: the scenario opening, the differentiators, the 170-word cap — extracted at peak convergence.
Overview
The clearest distillation signal a conversation produces is the explicit declaration: "this is the final version." Everything before it was the path; everything in force at that moment is the asset. This extraction targets that moment — the template-language rejection, the scenario-opening correction, the must-include differentiators, the word cap — and bottles the state the declaration blessed. This setup loads an App Store description chat ending in exactly that declaration, extracted at the moment of peak convergence.
Workflow
-
Catch the declaration
"This is the final version" is the extraction trigger — the state at that line is the asset.
-
Bottle everything in force
Rejections, corrections, constraints — all rules active at the declaration travel.
-
Revise from the bottle
Next quarter's update starts from the extracted prompt, not from archaeology.
Why This Works
- The declaration moment defines exactly what the conversation endorsed
- Extraction at convergence beats reconstruction from memory
- Bottled state makes future revisions incremental instead of archaeological
Best for
- Conversations ending in explicit final declarations
- High-polish copy with hard inclusion rules
- Assets that will be revised again next quarter
Not for
- Chats still mid-iteration — wait for convergence or accept Low confidence
- Tracking what changed between two prompt versions — the Prompt Version Diff
Use cases
- Capturing the final-version moment before it scrolls away
- Bottling store listings, landing copy, and launch text rules
- Extracting at peak convergence instead of from memory later