Back to the on-screen lesson ·
compare an act-focused and a rule-focused consequence argument
Paper packet. Every task here also exists on screen, where it is checked automatically; answers written on paper are not assessed by Nydus. When you are back at a device, enter your answers there.
You will compare an act-focused and a rule-focused consequence argument, explaining the inference and its limits in a supplied case.
A consequence argument must specify what it evaluates. A particular action and a generally accepted rule can have different comparison scores.
| Term | What it means |
|---|---|
| Act-focused criterion | A criterion evaluating available acts through their consequences in the case. |
| Rule-focused criterion | A criterion applying a rule justified through consequences of its general acceptance or following. |
| Decision procedure | A method a person uses to deliberate, distinct from the ultimate criterion of rightness. |
| Exception clause | A specified condition under which a general rule directs a different response. |
Two arguments can both care about consequences while evaluating different objects. An act-focused argument compares the consequences of the available actions in a particular situation. A rule-focused argument assesses a rule through the consequences of its general acceptance or following, then uses that rule to guide the particular action. The difference concerns the level at which the consequence comparison is made. It is not a contrast between caring about outcomes and ignoring them.
Suppose a shared workshop has a rule requiring people to return tools to the labeled shelf. In one instance, leaving a tool on a nearby bench might save a minute. An act-focused argument asks about the consequences of leaving it there in this case, including any later inconvenience. A rule-focused argument asks about a generally accepted practice of returning tools, including predictable access, reduced searching, and the burden of complying. Either argument may favor returning the tool, but the route to the conclusion differs.
Agreement in a case does not make the theories identical. Two different principles can recommend the same action because the facts align. To compare the principles, find a case in which their specified evaluations diverge or explain the different reasons they give for agreement. Likewise, disagreement about a recommendation does not show that one view has ceased to be consequentialist. Both may ultimately defend their criteria through outcomes while connecting those outcomes to action differently.
The classroom cases stipulate simplified act and policy scores. They ask you to reconstruct which criterion generates which result. They do not measure your willingness to obey rules or endorse an ethical theory. A learner can explain a rule-consequentialist argument accurately while questioning whether its favored rule handles an exceptional case well. Understanding the structure comes before judging whether the account succeeds.
Another way: Rules coordinate expectations
Rules can affect consequences partly through expectations. If everyone expects borrowed tools to return to a known place, they can plan their work without asking where each item went. The benefit is not simply the sum of isolated return acts described without their social context. A stable practice changes what others can reasonably anticipate and which coordination costs they face. A rule-focused account tries to include those wider effects.
Publicity also matters. A policy that works only when people do not know it may have different consequences from the same policy publicly announced. If participants learn that exceptions are granted whenever someone predicts a private advantage, trust in the general practice may weaken. This claim is empirical and should be supported rather than assumed. Still, it illustrates why a rule evaluation can consider effects beyond the visible convenience in one isolated episode.
Specify the implementation assumption. Is the comparison about everyone following a rule, most people accepting it, or a realistic level of compliance? These are different scenarios. A rule may look excellent under perfect adherence but perform poorly when it is difficult to understand or enforce. Some rule-consequentialist theories focus on the effects of internalizing or accepting a code rather than merely on a world of perfect outward compliance. The exercise must state which simplified model it uses.
The burden of learning and following a rule is itself a consequence. An extremely detailed code might handle every imaginable exception but be impossible for ordinary users to remember. A simpler policy may be less finely optimized yet lead to better outcomes through reliable use. This makes practicality relevant to rule evaluation without turning every existing custom into a justified rule. The rule still needs to be defended against feasible alternatives.
Another way: An act criterion can still recommend using rules
An act-consequentialist can recognize that people have limited time and information. Following a useful rule of thumb may often produce better results than attempting a fresh calculation in every situation. This is a distinction between the criterion of rightness and a decision procedure. The criterion says what ultimately makes an action right; the procedure says how a person should normally deliberate. Using rules as a procedure does not automatically make the ultimate criterion rule-consequentialist.
For example, a person might generally follow a return-tools rule because case-by-case calculations are unreliable and forgetting equipment has bad consequences. They may still hold that a particular act is right when it produces the best overall result, even if it departs from that usual rule. A rule-consequentialist, by contrast, can ground the act's rightness in conformity with a justified rule whose general acceptance has the best consequences. The distinction concerns what finally explains the moral assessment.
Do not caricature act reasoning as looking only at immediate benefits. A careful act-focused calculation can include effects on trust, precedent, and future behavior when this particular action is expected to cause them. Nor should rule reasoning be caricatured as blind attachment to any rule. Its rules are defended consequentially and can be compared or revised. The fair comparison gives both accounts their relevant evidence and asks where their criteria genuinely differ.
When a passage says 'usually follow this rule because it tends to work well', ask what it says about exceptions. Does the author ultimately evaluate each act by its consequences, or evaluate conformity to a consequence-justified code? If the passage does not answer, mark the classification as incomplete rather than guessing from the word 'rule'. Ethical terms should track argumentative commitments, not isolated vocabulary.
Another way: Exceptions, rigidity and collapse
A challenge to rule-focused accounts asks why a justified rule should be followed when breaking it would produce a better result in a particular case. The critic worries about rigidity: the rule appears to require a worse outcome despite being defended by consequences. The defender may answer that the apparent exception neglects effects on acceptance, error, or trust, or that a better rule includes a carefully stated exception. Each response should be examined on its own terms.
An opposite challenge asks whether adding enough exceptions makes the view collapse into act consequentialism. If the rule becomes 'do whatever has the best consequences in each particular case', then the rule no longer supplies a distinct criterion. A rule-focused theory needs an account of appropriate generality and exceptions that preserves its structure. This is a philosophical problem about the theory's identity and justification, not a simple objection that rules sometimes need revision.
An exception can be principled rather than merely convenient. A tool-return code might contain an emergency clause with a clear trigger and a later reporting requirement. The clause can itself be evaluated as part of the publicly accepted rule. A private excuse added only after someone wants to avoid an inconvenience is different. Compare the stated exception's scope, evidence requirements, and general consequences instead of treating every departure as equally justified or equally arbitrary.
Counterfactual policy comparisons also need a baseline. Compare general acceptance of rule R with acceptance of a feasible alternative S under the same assumptions. If R is modeled with perfect compliance while S is modeled with widespread confusion, the comparison may be unfair. Differences in understandability can be relevant, but they need explicit support. The exercise's simplified scores hold the scenario fixed so that the inferential role of the rule is visible.
Finish with two separate rankings when both are supplied: the ranking of acts under the immediate case model and the ranking of rules under the general-acceptance model. Then identify which ranking the argument treats as governing the particular recommendation. This avoids quietly borrowing an attractive number from one level and a conclusion from the other. A precise reconstruction keeps the theory's criterion and its factual assumptions connected throughout.
Another way: Do not equate an accepted rule with an ethical rule
A custom's popularity does not itself show that accepting it has the best consequences. A rule-focused argument needs a comparison with alternatives and an account of benefits and burdens, including those imposed on people with little influence over the custom. The same requirement applies to a newly proposed policy. Familiarity and novelty can affect implementation, but neither replaces the consequence argument that is supposed to justify the code.
Another way: A publicly stated exception can change expectations
If a workshop adopts an emergency exception, users should know what triggers it and where displaced tools will be recorded. Otherwise the exception may undermine the coordination benefits used to justify the main rule. Assess the whole communicated policy, including its exception procedure, rather than comparing an ideal rule with an undocumented private practice. The implementation details matter because they shape what others can reasonably expect.
A fictional workshop compares two publicly accepted tool policies using stipulated net consequence units. Policy R requires tools to be returned to labeled shelves before the borrower leaves. Its general-acceptance model gives thirty coordination-benefit units and eight compliance-burden units, for a net score of twenty-two. Policy S allows tools to be left wherever the borrower expects them to be found. Its model gives twenty convenience-benefit units and twelve search-burden units, for a net score of eight.
Under the supplied rule-consequentialist criterion, R is the preferred policy. In a particular late-evening case, a separate act model assigns six units to leaving a tool on a nearby bench and five to returning it. Under that stipulated act comparison alone, leaving it ranks higher. The two recommendations diverge because the exercise supplies distinct evaluative levels and explicitly asks which level governs the conclusion.
A careful discussion should question whether the isolated act model has omitted an actual effect on trust or future searching. If such effects belong to the particular act, they should be included in that model. But the learner should not silently change the supplied numbers to force agreement. First reconstruct the stipulated disagreement; then name the empirical assumption that might deserve revision in a real case.
The workshop might also compare a clear exception policy for unusual closing situations. Its general consequences, complexity, and effects on expectations would need assessment. Calling an exception 'practical' does not establish that it belongs in the best code, and calling the return requirement a 'rule' does not establish that it must never change. The lesson's bounded result is a map of two consequence arguments: one ranks the available acts in the stated case, and the other ranks publicly accepted rules and applies the preferred rule to that case.
Act reasoning need not ignore long-term effects, and rule reasoning need not defend every existing custom. Using a rule of thumb does not by itself identify the ultimate criterion. Preserve the level of evaluation, the implementation assumptions, and the treatment of exceptions before comparing the recommendations.
Identify the object of comparison.
General acceptance of policy R
The argument assesses a shared rule rather than one isolated return act.
Record the supplied coordination benefits.
30 units
These include effects of predictable access across the modeled practice.
Record the supplied compliance burdens.
8 units
Following and learning the rule also has consequences.
Calculate the rule's net score.
30 - 8 = 22
The supplied model subtracts the burdens from the general benefits.
Label the score's level.
A general-acceptance policy score
It must not be silently treated as the benefit of one isolated action.
Record policy R's net result.
22 units
This score comes from the supplied common general-acceptance model.
Record policy S's benefits and burdens.
20 benefit units and 12 burden units
The alternative is evaluated using the same kind of scenario.
Calculate policy S's net result.
20 - 12 = 8
The same arithmetic rule preserves comparability.
Compare the two policy scores.
R exceeds S by 14 units
The rule-focused criterion ranks the code with the better stipulated general consequences.
State the conditional recommendation.
Prefer R under this model
The ranking depends on the given effects and the rule-focused criterion.
Record the isolated act comparison.
Leave on bench: 6; return: 5
These are the stipulated consequences in one particular case.
Apply the act-focused ranking.
Leaving ranks higher by 1
The larger case score governs under the supplied act criterion.
Record the policy comparison.
Return policy R: 22; flexible policy S: 8
These scores concern general acceptance rather than only the one case.
Apply the rule-focused ranking.
R ranks higher by 14
The larger policy score determines the preferred rule.
Apply the preferred rule to the case.
Return the tool
The rule-focused recommendation follows conformity with the justified policy.
Identify the precise divergence.
Different evaluation levels govern the act recommendation
Both arguments appeal to consequences but connect them to right action differently.
The supplied act scores for A and B are nine and seven.
A minus B = 2
The act criterion favors the greater case score.
The supplied general-policy scores for A and B are eleven and sixteen.
A minus B = -5
The rule criterion favors the greater general-acceptance score.
Interpret the different signs.
For A/B, particular-act scores are 8/6 and general-policy scores are 10/15. Compute A minus B separately at each level, preserving negative differences.
| Response | |
|---|---|
| Act | |
| Rule |
The act scores for A/B are twelve and eight; the general-policy scores are fourteen and twenty. Complete the two-level comparison.
Subtract the act score of B from A.
Act difference = act
This calculation belongs only to the particular-action comparison.
Subtract the policy score of B from A.
Policy difference = rule
This calculation concerns the stipulated general-acceptance scenario.
Keep the differing rankings explicit.
The levels favor different options
The signs identify the divergence without changing either supplied model.
For A/B, particular-act scores are 4/7 and general-policy scores are 12/18. Compute each A-minus-B difference. Agreement in ranking does not erase the distinct criteria.
Act score A minus B: act. General-policy score A minus B: rule.
For A/B, particular-act scores are 9/9 and general-policy scores are 21/16. Compute A minus B at each level without resolving the act tie from the policy number.
Act score A minus B: act. General-policy score A minus B: rule.
For options A and B, particular-act scores are 8 and 12 while general-policy scores are 25 and 19. Under each supplied maximizing criterion, name the preferred option; then calculate the general-policy score A minus B. Do not mix levels.
| Your reconstruction | |
|---|---|
| Act choice | |
| Policy choice | |
| Policy difference |
In a fictional workshop, A means returning a tool and B means leaving it on a bench. The stipulated particular-act scores are A=5, B=6; the general-acceptance policy scores are A=22, B=8. Reconstruct A minus B at each level before evaluating the assumptions.
Act score A minus B: act. General-policy score A minus B: rule.
Lesson test: one question per skill, one attempt each, no hints. Your answers are checked when you submit.
Two supplied options A/B have particular-act scores 13/9 and general-policy scores 17/24. Compute A minus B separately at each level. The act and rule arguments use their respective score types rather than borrowing the favorable number from the other.
Act score A minus B: act. General-policy score A minus B: rule.
Without rereading, explain how to compare an act-focused and a rule-focused consequence argument. Give a fresh case and identify what would change your analysis.
10. Finish a divergent comparison, step 3
Act level favors A; policy level favors B
The criteria disagree in the stipulated model without ceasing to concern consequences.