Proof Strategies
Learning objectives
- Identify the logical form of a goal and choose an appropriate proof strategy
- Distinguish between givens and goals in a proof
- Construct a direct proof of a conditional statement
- Organize a proof using the structured approach of analyzing givens and goals
How does a mathematician turn a vague hunch — "I think this is true" — into a permanent fact the entire community will accept? By writing a proof: a step-by-step argument that begins from accepted truths (axioms, definitions, prior theorems) and ends, by undeniable logic, at the conclusion. Chapter 3 is the heart of the course because here we stop talking about logic and start doing mathematics. The structured approach you will learn — analyse the goal, choose a strategy, work the gap from both ends — is exactly how working mathematicians draft proofs, and exactly how proof assistants like Coq and Lean check them. Master this skeleton and the rest of the chapter is variations on a theme.
Givens and goals
The most fundamental distinction in proof-writing is between givens — statements you already know (or have assumed) to be true — and the goal, the statement you are trying to prove. The entire art of proof is figuring out how to bridge the gap. At every step you should be able to point to your current givens list and your current goal and say: "I am here, I want to be there."
Givens grow as the proof progresses (each derived step adds to them). Goals can shrink and transform: assuming the hypothesis of an implication moves it onto the givens side; letting a variable be arbitrary peels off a universal quantifier from the goal. Watching the givens/goal pair evolve is how you stay oriented inside a long proof.
The direct proof template
The direct proof is the most natural strategy for proving a conditional . The skeleton is:
- Assume (add it to your givens).
- Use definitions and known results to derive intermediate facts.
- Conclude .
Each line must follow logically from earlier givens. "Therefore," "so," and "hence" are not decorative — they are claims that the next line is a logical consequence of what came before. If a reader cannot reconstruct the reasoning for any step, the proof is broken.
The structured approach
Before writing any prose, do the bookkeeping:
Step 1. Write your givens and your goal explicitly. Step 2. Analyse the logical form of the goal. Step 3. Choose a strategy matched to that form. Step 4. Apply the strategy — this transforms givens and goal. Step 5. Repeat until givens entail the goal.
Strategies are chosen by the form of the goal: → direct proof, → arbitrary , → exhibit a witness, → prove each conjunct, → prove one disjunct or assume the negation of the other. The full menu of strategies is the rest of this chapter.
Working from both ends
Experienced provers work forward from givens (what new facts can I derive?) and backward from the goal (what would suffice to conclude it?) until the two directions meet. The final written proof reads forward, but the discovery process is bidirectional. If you stare at the goal and feel stuck, ask: "what is the form of this goal, and what is the standard move for that form?" Then make that move and see what new goal you face.
Pause and think: Suppose your goal is "If is an integer, then is even." What are your givens? What is the form of the goal? Which strategy does that form suggest? (Hint: there is an outer universal and an inner conditional. Peel them in order.)
The shape of a proof, visualized
Every proof has a tree structure: the goal at the root, decomposed step by step into sub-goals and finally into premises at the leaves. The widget below builds proof trees one layer at a time for four canonical proofs (direct, contrapositive, contradiction, existence). Watch how the goal decomposes — that decomposition is the strategy.
Try it
- For each statement, identify givens, goal, and the matching strategy before writing a single line of proof: (a) "If , then ." (b) "For all integers , is even."
- Predict first: in the direct proof of "if and are even, then is even," what is the very first line you write after "Assume the hypothesis"?
- Spot the flaw: a student writes "Suppose is even. Then is even, and is even. So if is even then is even." What strategy did they violate?
- Work backward: to prove , what definition of "divides" must you end at? Now work forward: what does the given tell you in symbolic form?
- Skeleton-only: write the first sentence and the last sentence of a direct proof of "if and , then ." Do not fill in the middle.
A trap to watch for
The single most common rookie mistake is to prove by example: substituting one concrete value for an arbitrary variable and declaring the universal proved. "Let be an arbitrary integer. Take : then is even..." is not a proof — it shows the claim holds for one integer, not all of them. The word "arbitrary" in a proof means: I am about to do the proof in a way that uses no special property of this object beyond its membership in the domain. If your argument uses the fact that equals a specific number, you have not proved the universal. Examples are useful for building intuition and finding counterexamples, but they cannot replace a general argument.
What you now know
You can take any mathematical statement, identify its givens and goal, analyse the logical form of the goal, and choose a proof strategy that matches. You know the direct-proof template for conditionals and the structured-approach bookkeeping that keeps long proofs from wandering. The remaining sections of this chapter are each a specialisation: contradiction and contrapositive for conditionals you cannot crack directly, quantifier strategies for "for all" and "there exists," and case analysis for disjunctions. Every one of them slots into the same structured-approach skeleton.
References
- Velleman, D. J. (2019). How to Prove It: A Structured Approach (3rd ed.). Cambridge University Press, §3.1.
- Polya, G. (1957). How to Solve It: A New Aspect of Mathematical Method. Princeton University Press.
- Hammack, R. (2018). Book of Proof (3rd ed.). Open-source textbook, ch. 4.
- Solow, D. (2014). How to Read and Do Proofs (6th ed.). Wiley, ch. 1–3.
- Pierce, B. C. et al. (2018). Software Foundations, Vol. 1: Logical Foundations. Online textbook (Coq), ch. "Logic."