No line between proposing and doing

What it looks like. Proposals, hypotheticals, drafts, and simulations are represented the same way as decisions and actions. Whether something is contemplated or committed is carried by surrounding phrasing rather than by an architectural tag.

Why it fails. The distinction is load-bearing at exactly one boundary — the one where a plan becomes a tool call — and phrasing does not survive that crossing reliably.

Instead. Require modal-state tagging on artifacts crossing the planner/executor boundary and gate tool execution on the declared state. Audit for artifacts that crossed with the tag missing.