Why a proposal is written to pass, not to be debated

A proposal reached the DAO already shaped to pass: a leading title, a summary listing only benefits, a single recommended option, and objections relegated to a section few would reach. The drafting was not neutral description but persuasion, engineered so that reading it produced agreement. Debate was invited in form, but the document had pre-decided the conclusion. A proposal written to be debated exposes trade-offs; one written to pass hides them behind framing that makes yes the path of least resistance.

What everyone sees

A voter reads a clear, confident proposal and feels informed: the case is laid out, the recommendation is sensible, agreement feels natural. The clarity reassures. The voter treats the document as a neutral briefing, not as an advocacy piece, and does not notice that the framing, the omitted counterarguments and the single highlighted option have arranged his consent before he has weighed anything himself.

What is actually happening

Research on choice architecture and framing shows that how an option is presented strongly determines whether it is chosen, independent of its merits. A proposal that leads with benefits, buries costs, and offers one recommended path exploits default and framing effects to manufacture assent. Genuine deliberation requires balanced presentation of alternatives; a document optimised to pass is optimised to suppress exactly the comparison that deliberation needs.

Why it stays hidden

The hidden mechanism is persuasion disguised as description. The proposal looks like information but functions as advocacy, using framing, omission and a steered default to produce the vote it wants. The voter experiences reasoned agreement while the reasoning was pre-arranged by the drafting. The theatre is a debate over a document that has already decided the debate.