Constitutional Basics for DReps

This lesson is about a distinction that sounds obvious in the abstract and is violated constantly in practice: the difference between asking whether governance may do something and asking whether governance should do it. Representatives who cannot hold those apart end up writing rationales that persuade nobody, because every objection is inflated into a constitutional crisis and every constitutional problem is softened into a matter of taste.

The Cardano Constitution exists because on-chain governance can change things that are extremely hard to reverse: protocol parameters, the treasury, the composition of the Constitutional Committee, the rules of governance itself. A system able to change its own rules by simple majority is a system with no stable commitments. The constitutional text is the mechanism by which the community pre-commits: certain changes are out of bounds, certain changes require stronger conditions, and certain changes must be justified against a written standard rather than an argument made in the moment.

Read that way, the text is a floor, not a programme. It tells you what may not happen. Inside the remaining space, it is deliberately quiet.

It does not tell you what the treasury is for, which ecosystem strategy is correct, whether a given team deserves funding, or how much decentralisation is enough. Those are the questions representatives exist to answer, and the constitution refuses to answer them on your behalf.

This has a practical consequence that surprises new DReps. Most of the work of representation happens in constitutionally uncontroversial territory. Many of the actions you will assess raise no constitutional question at all and still demand hard judgement. If your reading process only detects constitutional violations, it will report nothing useful most of the time.

Four common expectations the constitutional framework does not satisfy, each of which produces a characteristic mistake:

That last point is the one the Institute treats as non-negotiable. A constitutional reading narrows the set of permissible outcomes. It never selects among them for you, and nobody - including this course - should present it as though it does.

Notice what the separation buys you. The proposer can answer the merit objection by producing rates and tightening deliverables. They cannot answer a constitutional accusation, because there is nothing to answer. Misclassifying your objection removes the possibility of the proposal being improved, which is usually the outcome you actually wanted.

You now have a three-way separation that the rest of this course depends on. Constitutionality is a bounded, checkable question answered against a specific text and version. Merit is an open judgement about quality, cost and risk that the text deliberately leaves to representatives.

Preference is what remains once both are settled. Every classification you produce in later lessons will be sorted into those three buckets, and every claim in the first bucket will carry a citation.

Several things are genuinely unsettled and this lesson does not pretend otherwise. How interpretive language such as reasonable or proportionate will be applied in contested cases is not fixed; it accumulates through practice. How the constitutional framework itself evolves, and how earlier readings survive amendment, is an open question.

And whether a specific guardrail applies to a specific novel action is often arguable - which is why the classification lab asks you to record the argument on both sides rather than assert a conclusion.