From 430ea239dd47268cce1aa72ec4b24b46f886a756 Mon Sep 17 00:00:00 2001 From: Aaron Nelson Date: Wed, 20 May 2026 01:06:40 +0000 Subject: [PATCH] =?UTF-8?q?api.py:=20drop=20save=5Fdocument=20preview=20es?= =?UTF-8?q?cape=20hatch=20=E2=80=94=20two-turn=20separation=20now=20uncond?= =?UTF-8?q?itional?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Previous prompt let Aaron skip the preview if he asked up front. The trigger phrasing "output it as docx" was lexically too close to "output as docx" in a normal request, so Claude treated 'create a one-page bio and output as docx' as a one-shot save and wrote the file before Aaron could see it. Removed the escape hatch. Draft-then-commit is now the only flow. --- scripts/api.py | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/scripts/api.py b/scripts/api.py index c4d4c9e..7c0c5cc 100644 --- a/scripts/api.py +++ b/scripts/api.py @@ -143,15 +143,16 @@ irrelevant hits rather than forcing them into the answer. When Aaron asks for a document file — bio, cover letter, statement, CV section, anything he wants to send or edit outside chat — produce -the full text as your chat reply first so he can read it, push back, -and iterate. Do NOT call save_document on the first pass. Wait for -him to commit ("save it", "yes write it out as docx", "good, output -it") and only then call save_document with the finalized content. If -he asks for edits — "tighten the second paragraph", "drop the -exhibitions list" — keep iterating in chat; only call save_document -once he explicitly approves the version. The one exception: if he -says up front to skip the preview ("just save a bio as docx, no -preview needed"), honor that. +the full text as your chat reply first. NEVER call save_document on +the same turn as the initial request, even when Aaron's phrasing +includes words like "save", "output", "write", or "as docx/pdf" in +the original ask. Those are part of the topic, not a save approval. +The first call to save_document only happens in a *later* turn, +after Aaron has read the draft and explicitly approves it — examples: +"save it", "yes save it", "looks good, write it out", "go ahead". +If Aaron asks for revisions, iterate in chat without calling +save_document. The two-turn separation (draft, then commit) is +unconditional — there is no escape hatch. Use web search automatically when current external information is needed. Never re-brief on context that's already in memory or