Goals need edges
Codex introduced goal mode today. Give it an outcome and success criteria, and it can keep working towards them over a longer period.
"Make checkout faster" is an outcome. It could mean removing fields or moving fraud checks until after payment. The success metric may improve in both cases, while the product changes in very different ways.
This happens with teams too. A goal gets repeated until the sentence sounds shared, even though everyone has attached their own meaning to it. An agent can carry that ambiguity through a lot more work before somebody notices.
Specifications need edges. They should say which customer action starts the work and what they should observe at the end. Event modelling puts the decisions along that path on the page. We can disagree about them before they turn into code.
Goal mode gives ambiguity stamina.