daily-held: default chat-drafted programs to advisory readou
Highlight text on any card (body, plan, or an event) to anchor a comment, or leave a whole-task comment here. Mention @claude to summon a reply.
No comments yet.
Overview / Motivation
Auto-filed by the /daily 2026-07-28 problem sweep (transcript miners over the day's 55 session transcripts). Source: group-H P1. Held under the judgment-call carve-out: genuinely ambiguous intent — generalizing a single correction into a standing default is a design preference only Thomas can set.
The held item
In a 2026-07-28 planning chat, a drafted program included a mid-program kill-switch decision point; Thomas rejected it: "don't treat it as a kill switch. just run it then continue till the end no matter what" (plus one over-compressed plan line he had to ask about). If this preference is general — mid-program readouts should be ADVISORY, not gating, for chat-drafted programs — it belongs as a standing clause; if it was specific to that program, no change.
Suggested action
One-line answer: "generalize" → a route-2 filing adds the clause to the chat-drafting guidance; "one-off" → close this task.