Read
Build the mental model
Move through the guided explanation first so the central distinction and purpose are clear before you evaluate your own work.
Natural Deduction
Capstone: Building and Defending a Complete Deductive Argument
An integrative lesson that asks students to move through the full cycle of deductive evaluation: read an argument in ordinary language, symbolize it, classify its validity, either prove it or refute it with a counterexample, and then explain the result in plain English.
Read the explanation sections first, then use the activities to test whether you can apply the idea under pressure.
Start Here
What this lesson is helping you do
An integrative lesson that asks students to move through the full cycle of deductive evaluation: read an argument in ordinary language, symbolize it, classify its validity, either prove it or refute it with a counterexample, and then explain the result in plain English. The practice in this lesson depends on understanding Validity, Soundness, Entailment, and Proof and applying tools such as Modus Ponens and Modus Tollens correctly.
How to approach it
Read the explanation sections first, then use the activities to test whether you can apply the idea under pressure.
What the practice is building
You will put the explanation to work through guided problem solving and quiz activities, so the goal is not just to recognize the idea but to use it under your own control.
What success should let you do
Complete the full evaluation cycle for at least 3 integrative cases, producing a translation, validity classification, proof or counterexample, and plain-English explanation for each.
Reading Path
Move through the lesson in this order
The page is designed to teach before it tests. Use this sequence to keep the reading, examples, and practice in the right relationship.
Study
Watch the move in context
Use the worked example to see how the reasoning behaves when someone else performs it carefully.
Do
Practice with a standard
Only then move into the activities, using the pause-and-check prompts as a final checkpoint before you submit.
Guided Explanation
Read this before you try the activity
These sections give the learner a usable mental model first, so the practice feels like application rather than guesswork.
Framing
The full cycle of deductive evaluation
Until now, each lesson has trained one move in isolation: separate truth from validity, symbolize, prove, or diagnose. The capstone asks you to run the whole cycle in order on a single argument. Reading, symbolizing, classifying, proving or refuting, and explaining are all one continuous act of evaluation.
The reason this matters is that, in practice, arguments do not arrive pre-labeled. You have to decide which move comes next. This lesson trains the transitions: when to stop symbolizing and start proving, when to stop searching for a proof and start building a counterexample, and when to stop proving and write the explanation.
What to look for
- Translate before you judge.
- Judge validity before you search for a proof.
- Switch to counterexample construction the moment a proof attempt stalls for a structural reason.
Real deductive evaluation is a single continuous pipeline; the capstone trains the handoffs between its stages.
Strategy
A working pattern for integrative cases
Use a fixed pattern: (1) translate with a sentence-letter key, (2) state the target conclusion, (3) look at the symbolic form and ask whether any standard valid pattern applies, (4) if yes, construct the proof; if no, try to build a counterexample. (5) Write a plain-English explanation of the result.
The discipline of this pattern is that it prevents a very common failure: getting stuck half-proving an invalid argument because you never stepped back to check whether it was valid in the first place. If your proof attempt is not making progress after two or three moves, do not push harder; build a counterexample instead.
What to look for
- Translate, then classify, then attempt proof or refutation.
- Switch strategies when a proof stalls for structural reasons.
- Close with a one-paragraph plain-English explanation.
A fixed pipeline keeps you from confusing a stuck proof attempt with a hard proof.
Error patterns
How integration failures look
Students who master each skill in isolation often still fail on integrative cases. The commonest failure is skipping the classification step: jumping straight from translation to proof-building without first asking whether the argument is valid. If it is not, no proof will ever succeed, and the student burns time before giving up.
The second commonest failure is writing a correct proof but failing to explain it in ordinary English. A deductive argument is only useful when you can tell a non-logician why the conclusion follows. The explanation is not decoration; it is the output of the whole process.
What to look for
- Do not skip the validity classification.
- Do not treat the proof as the end of the work.
- Always write the plain-English explanation last.
Integration failures cluster around skipped classification and missing explanations; both are preventable with discipline.
Before practice
What this lesson is testing
The cases below each require at least three of the unit's skills in combination. You will need to symbolize correctly, judge validity, prove or refute, and then write a short explanation. A case is only complete when all four outputs are present.
Treat the capstone as a rehearsal for how you will evaluate arguments when no one has told you which tool to use. The point is not to be fast; the point is to run the pipeline cleanly and to stop and switch strategies when a move stalls.
What to look for
- Produce all four outputs for every case.
- Change strategies when a proof attempt stalls structurally.
- Treat the explanation as the final output, not an afterthought.
The capstone measures how cleanly you run the full pipeline under conditions where no step has been prescribed.
Core Ideas
The main concepts to keep in view
Use these as anchors while you read the example and draft your response. If the concepts blur together, the practice usually blurs too.
Validity
The property of an argument whose conclusion cannot be false while all its premises are true.
Why it matters: Validity is the central standard of deductive evaluation, and in propositional logic it can be mechanically tested.
Soundness
A deductive argument is sound when it is valid and all of its premises are true.
Why it matters: Soundness helps students distinguish logical structure from the actual truth of premises.
Entailment
A relation in which the premises, taken together, guarantee the conclusion.
Why it matters: Entailment explains why a valid deduction gives necessity rather than probability.
Proof
A rule-governed derivation showing that a conclusion follows from a set of premises.
Why it matters: Proof is the main formal tool used to establish deductive validity.
Subproof
A nested section of a proof used to track assumptions and scope in conditional or indirect derivations.
Why it matters: Subproof structure is essential for handling assumptions correctly in natural deduction.
Counterexample
A situation in which the premises of an argument are all true while the conclusion is false.
Why it matters: Producing a counterexample is one of the cleanest ways to show an argument is invalid.
Reference
Open these only when you need the extra structure
How the lesson is meant to unfold
Review
This step supports the lesson by moving from explanation toward application.
Guided Synthesis
This step supports the lesson by moving from explanation toward application.
Independent Synthesis
This step supports the lesson by moving from explanation toward application.
Reflection
This step supports the lesson by moving from explanation toward application.
Mastery Check
The final target tells you what successful understanding should enable you to do.
Reasoning tools and formal patterns
Rules and standards
These are the criteria the unit uses to judge whether your reasoning is actually sound.
Modus Ponens
From 'P → Q' and 'P', one may derive 'Q'.
Common failures
- The student affirms the consequent by deriving 'P' from 'P → Q' and 'Q'.
- The student derives 'Q' from 'Q → P' and 'P' after confusing the direction of the conditional.
Modus Tollens
From 'P → Q' and '¬Q', one may derive '¬P'.
Common failures
- The student denies the antecedent by deriving '¬Q' from 'P → Q' and '¬P'.
- The student ignores the conditional's direction when the negation is placed on the consequent.
Hypothetical Syllogism
From P -> Q and Q -> R, infer P -> R.
Common failures
- The chained conditionals do not actually share a middle term.
- The derived conditional swaps antecedent and consequent.
Disjunctive Syllogism
From 'P ∨ Q' and '¬P', one may derive 'Q'; similarly from 'P ∨ Q' and '¬Q', one may derive 'P'.
Common failures
- The student derives the negated disjunct instead of the remaining disjunct.
- The student assumes an exclusive disjunction and draws an unlicensed inference about the second disjunct.
Conjunction Introduction
From P and Q, infer P & Q.
Common failures
- One of the conjuncts was not established on a prior line.
- The conjunction changes the content of the cited lines.
Conjunction Elimination
From P & Q, infer either P or Q.
Common failures
- The cited line is not a conjunction.
- The derived statement is not one of the conjuncts.
Conditional Introduction
If assuming P lets you derive Q within a subproof, you may discharge the assumption and infer P -> Q.
Common failures
- Discharging the assumption before Q has actually been derived.
- Using lines from inside a closed subproof after its assumption has been discharged.
Necessity Standard
A deductive conclusion must follow necessarily from the premises, not merely appear plausible.
Common failures
- The student defends a conclusion on the basis of plausibility alone.
- The student confuses a likely conclusion with a logically guaranteed one.
Patterns
Use these when you need to turn a messy passage into a cleaner logical structure before evaluating it.
Sentence-Letter Translation
Input form
natural_language_argument
Output form
symbolic_argument
Steps
- Identify the atomic statements in the argument.
- Assign a sentence letter to each distinct atomic statement.
- Identify the logical connectives in each premise and the conclusion.
- Translate each premise and the conclusion into symbolic form.
- Check that the symbolic form preserves the original logical structure.
Watch for
- Using different letters for the same atomic statement in different places.
- Mistranslating conditionals by reading 'only if' as 'if'.
- Representing surface grammar instead of underlying logical form.
Natural Deduction Proof Format
Input form
symbolic_argument
Output form
line_by_line_proof
Steps
- List the premises as the first numbered lines.
- State the target conclusion.
- Add justified lines one at a time, citing the rule and the prior lines used.
- Open a subproof whenever you need to make an assumption.
- Close each subproof by discharging its assumption with the appropriate rule.
- Verify that the final line matches the intended conclusion and that every citation is in scope.
Watch for
- Citing lines that do not match the pattern of the chosen rule.
- Using a line inside a closed subproof after the assumption has been discharged.
- Skipping intermediate steps so that the rule cannot be verified.
Counterexample Construction
Input form
symbolic_argument
Output form
row_of_truth_values
Steps
- List the atomic letters that appear in the argument.
- Search for an assignment of truth values that makes every premise true.
- Check whether that same assignment also makes the conclusion false.
- If such an assignment exists, present it as the counterexample.
Watch for
- Claiming a counterexample without actually satisfying all premises.
- Overlooking rows that make the conclusion false by coincidence of truth values.
Worked Through
Examples that model the standard before you try it
Do not skim these. A worked example earns its place when you can point to the exact move it is modeling and the mistake it is trying to prevent.
Worked Example
Full-Cycle Walkthrough
A full-cycle answer includes every stage, not just the proof. The explanation in plain English is what lets a non-logician trust the result.
Argument
- If the vendor ships on time, the launch proceeds on schedule.
- If the launch proceeds on schedule, the marketing campaign starts Monday.
- The vendor shipped on time.
- Therefore the marketing campaign starts Monday.
Proof Sketch
- 1. V -> L (premise)
- 2. L -> M (premise)
- 3. V (premise)
- 4. L (modus ponens, 1 and 3)
- 5. M (modus ponens, 2 and 4)
Symbolic Form
- V -> L
- L -> M
- V
- therefore M
Classification
Valid.
Sentence Letter Key
L
The launch proceeds on schedule.
M
The marketing campaign starts Monday.
V
The vendor ships on time.
Plain English Explanation
The argument chains two conditionals with the first antecedent asserted. Once the vendor ships on time, the first conditional gives us the launch, and the second gives us the marketing campaign. The conclusion follows necessarily.
Pause and Check
Questions to use before you move into practice
Self-check questions
- Did I produce all four outputs for each case?
- Did I decide whether to prove or refute before I started writing the proof?
- Does my plain-English explanation make sense to someone who does not know the notation?
Practice
Now apply the idea yourself
Move into practice only after you can name the standard you are using and the structure you are trying to preserve or evaluate.
Guided Problem Solving
DeductiveFull-Cycle Deductive Evaluation
For each argument, carry out the complete evaluation cycle. Produce: (1) a sentence-letter key and symbolic form, (2) a validity classification, (3) either a natural-deduction proof OR a counterexample, and (4) a one-paragraph plain-English explanation of the result.
Integrative cases
Work each case all the way through before moving to the next. The cases are mixed: some are valid and some are invalid. Deciding which is part of the exercise.
Case A
If the budget proposal passes, the department will hire two engineers. If the department hires two engineers, the release will ship by September. The budget proposal passed. Therefore the release will ship by September.
Chain of conditionals with the first antecedent asserted.
Case B
If a patient responds to the drug, their inflammation markers decrease. Maya's inflammation markers decreased. Therefore Maya responded to the drug.
Watch which direction the conditional runs before you start proving.
Case C
Either the deployment used the new pipeline or the deployment was manual. The deployment did not use the new pipeline. If the deployment was manual, a human initiated it. Therefore a human initiated the deployment.
Combine disjunctive syllogism with a second conditional step.
Case D
If the experiment is well-designed, the results will be reproducible. The results are reproducible. So the experiment is well-designed.
Before you try to prove, ask whether any world satisfies the premises with the conclusion false.
Case E
All compilers that pass the conformance suite implement the standard correctly. The Gamma compiler passes the conformance suite. The Gamma compiler has a bug in its generics handling. Therefore some compiler that implements the standard correctly has a bug in its generics handling.
Mix quantified claims with a property ascription and decide whether the conclusion follows.
Proof Draft
LineStatementJustificationAction
1
2
3
Quiz
DeductiveCapstone Check Questions
Answer each short check question in one or two sentences. These questions test whether you can articulate the reasoning you just performed.
Check questions
Answer each question from memory and in your own words. No single question should need more than two sentences.
Question 1
Why does a counterexample refute a deductive argument, while a true conclusion does not confirm it?
The asymmetry between validation and refutation.
Question 2
What is the correct order of operations when you encounter a new argument in ordinary language?
Translate, classify, prove or refute, explain.
Question 3
When should you stop trying to build a proof and switch to building a counterexample?
Structural stall, not fatigue.
Question 4
Why is the plain-English explanation the last output of the pipeline rather than an optional add-on?
Argument evaluation is only useful when the result is communicable.
Proof Draft
LineStatementJustificationAction
1
2
3
Proof Constructor
Build a formal proof step by step. Add premises, apply inference rules, cite earlier lines, and derive your conclusion.
Add premises and derived steps above, or load a template to get started.
\u2588 Premise\u2588 Derived step
Symbols:\u00AC not\u2227 and\u2228 or\u2192 if-then\u2194 iff\u2234 therefore
Animated Explainers
Step-by-step visual walkthroughs of key concepts. Click to start.
Read the explanation carefully before jumping to activities!
Further Support
Open these only if you need extra help or context
Mistakes to avoid before submitting
- Burning time on a proof attempt for an invalid argument.
- Forgetting that the output of deductive evaluation is a communicable result, not just a proof.
Where students usually go wrong
Skipping classification and going straight to proof-building.
Treating a stalled proof as a hard proof rather than as evidence of invalidity.
Producing a correct proof but no plain-English explanation.
Writing an explanation that is just the symbolic proof translated word-for-word rather than a genuine paraphrase.
Historical context for this way of reasoning
Gottlob Frege
Frege insisted that logic was valuable precisely because it let you separate the form of an argument from its subject matter and then communicate the result back into ordinary language. The capstone exercise is a small-scale rehearsal of that project.