Rule Consequentialism (article)

This entry develops the distinction between assessing particular acts and selecting a code for its consequences. It considers welfare and other goods, how a code’s acceptance is modeled, and why predictable rules can matter even when an isolated exception looks attractive.

Keep a distinction between the criterion used to select the code and the guidance people use in ordinary action. A code may be justified by consequences while telling an individual to keep a promise without calculating every alternative anew. That distinction can explain why reliable expectations matter. As you read, note the assumptions about acceptance, learning, and enforcement, because a code evaluated under ideal conditions may work differently when people have limited information and uneven power.

Start with the sections on full rule consequentialism and its formulation. Note what is being compared: codes, acceptance rates, or individual acts. Then follow the discussion of objections and ask whether the proposed rules explain a familiar duty such as keeping a promise.

Carry forward the tension between stability and exceptions. Which code would people be able to learn and use? Would allowing every apparently beneficial violation erase the difference from act consequentialism? A mention of a thinker or case in the entry does not establish the author’s agreement with it.

For a reading exercise, compare a simple return rule in a lending service with an exception for emergencies. Ask what would happen if everyone could redefine an exception whenever late return seemed beneficial. Then ask what happens if no exception is possible. This original example exposes the tension between flexibility and predictability. Use the entry to examine the argument for a workable code, rather than treating either rule-following or local benefit as automatically decisive.