A latticework reading of Ashley Hodgson's economics explainer on prescriptive vs. proscriptive rules — why the direction of a rule changes almost everything about enforcement, compliance, and design.
Ashley Hodgson — Mature Economics: rules, obligations, and prohibitions
Ashley Hodgson's distinction sounds like vocabulary until you sit with it for a moment. Prescriptive rules — you must do this — and proscriptive rules — you must not do this — seem like two ways of saying the same thing. But the direction changes almost everything: what counts as compliance, how you detect a violation, who bears the burden of proof, and what space of behavior the rule leaves open. For the latticework, this is not a terminological footnote. It is a design choice that recurs in every domain where rules govern behavior.
Legal systems rely on both, but they weight them differently. Common law has historically favored proscription: the list of what you cannot do is long; the list of what you must do is short. Continental legal traditions lean more prescriptive. Moral philosophy has debated the distinction for centuries: the difference between a positive duty (you are obligated to help) and a negative duty (you are obligated not to harm) is one of the deepest fault lines in ethics.
System designers face the same fork. An API can specify exactly what requests must look like (prescriptive), or it can specify what requests are prohibited (proscriptive). A safety policy can mandate specific procedures (prescriptive) or enumerate prohibited actions (proscriptive). The choice determines how the system fails, how it is audited, and how much autonomy it grants to agents operating within it.
Framing effects — the well-established finding that logically equivalent choices feel different depending on how they are presented — apply at the level of rule structure. A rule that says "you must save a drowning person if you can" is logically related to a rule that says "you must not let a drowning person die if you can prevent it." But they feel different. The prescriptive version makes inaction visible as a violation; the proscriptive version makes action visible as compliance. The same underlying moral commitment generates different compliance psychology depending on direction.
The distinction also sharpens the model of incentive design. Prescriptive rules create a mandatory floor: you must meet this standard, at minimum. Proscriptive rules create a prohibited ceiling: you must stay below this line. In between — for proscriptive rules — is a space of unconstrained discretion. A workplace rule that says "you must not commit fraud" leaves enormous latitude for everything else. A workplace rule that says "you must follow this expense reporting procedure" specifies behavior precisely. Incentive designers who treat these as equivalent will be surprised when proscriptive rules generate creative compliance and prescriptive rules generate resentment.
Finally, moral philosophy's long-running dispute between consequentialists and deontologists partly tracks this distinction. Consequentialists tend to generate both kinds of rules (maximize good, minimize harm); strict deontologists often favor proscriptive side constraints (there are things you simply cannot do, regardless of consequences). Ashley's taxonomy maps neatly onto a divide that has occupied philosophers since Kant.
The most common assumption that this video quietly dismantles is that rules are fungible — that any rule can be restated in either direction without loss of meaning. In formal logic, this is often true: "do X" and "don't not-do X" are equivalent statements. But in practice, the direction determines where the enforcement burden falls. A prescriptive rule (must file taxes by April 15) requires the state to prove inaction: did you fail to file? A proscriptive rule (must not commit tax fraud) requires the state to prove a specific act. These are different evidentiary standards with different enforcement costs.
The model of symmetry between action and omission also bends here. Philosophers have long debated whether there is a morally relevant difference between doing harm and failing to prevent harm. Ashley's drowning example lands directly on this fault line: if you are prescriptively obligated to save a drowning person, then failing to jump in is a wrong act — an omission that carries the weight of commission. But in most legal systems, omissions are treated far more leniently than acts. The proscriptive tradition — do not harm — has generally won in law, if not in ethics.
The third implicit contradiction is to the idea that more specific rules are better rules. Prescriptive rules are highly specific (file by April 15; save all receipts). But that specificity is also fragility: every edge case not covered is a gap. Proscriptive rules leave enormous space open, which feels like underspecification but is often robustness: the rule holds even when the situation is novel.
The clearest new model this video proposes is rule directionality: the same underlying value — do not let your neighbor be harmed — can be expressed as a prohibition ("do not steal") or as a mandate ("help your neighbor when they need it"). The direction is not cosmetic. It determines the default behavior (compliance vs. non-compliance), the enforcement mechanism (proving absence vs. proving presence), and the space of permissible variance. When evaluating any rule, ask which direction it runs before evaluating its content.
The drowning thought experiment introduces a second model worth naming: ability-conditioned obligation. Ashley asks whether the prescriptive obligation to save a drowning person scales with swimming ability. If you can't swim, there is no obligation. If you can swim, there is. This is a common structure in moral and legal reasoning that rarely gets a clean label: the existence and weight of a positive duty depends on the capacity of the duty-holder. Doctors have prescriptive obligations to treat that non-doctors do not. Pilots have prescriptive obligations about emergency procedures that passengers do not. The model generalizes: prescriptive obligations are always conditioned on capability, even when the rule does not say so explicitly.
Finally, action space vs. prohibition space: proscriptive rules define a prohibition space (a closed set of forbidden acts) and leave action space open (everything else is permitted). Prescriptive rules close the action space by specifying what must happen and treat everything else as potentially non-compliant. System designers, legal drafters, and policy writers are always choosing between these two topologies. Proscriptive design grants more autonomy and is more robust to novel situations; prescriptive design is more auditable and produces more predictable behavior. Neither is universally superior; the choice should be explicit.
Ashley's two-minute taxonomy is not the conclusion of a long argument — it is a foundation for the next argument. Once you can name the direction a rule runs, you can ask why it runs that way, whether a different direction would serve the underlying value better, and what behavior the current direction incentivizes at the margin. Those are the questions that matter in policy, in system design, and in ethics.
If it says you must do this, and if you don't act in a certain way there will be consequences — that's prescriptive. If it says you must not do this, and if you do act in a certain way there will be consequences — that's proscriptive. — Ashley Hodgson, Mature Economics
The latticework contribution is small but precise: a clean vocabulary for a distinction that was previously operating unnamed in most readers' thinking. The most useful models are often not new truths but new handles on things we already knew. Rule directionality is one of those handles — once you have it, you cannot stop seeing which way every rule you encounter is running.