How to Study Mathematical Proofs From Lecture Slides
A proof on a lecture slide can look obvious while it is in front of you. Close the deck and you may remember the conclusion without knowing how to reach it. Study the chain of reasons: what is assumed, what each step uses, and why the final statement follows.
This guide is for reconstructing a proof taught in your course. It is distinct from memorizing a formula or tracing an algorithm. The ledger below is a paper or manual note-taking template; it does not claim that Notoo verifies proofs.
Capture the claim before the calculation
Keep the original slide or permitted PDF open. Copy the exact statement, including its domain and qualifiers. “For every integer” differs from “there exists an integer”; “if” differs from “if and only if.” Record the slide number and deck version.
MIT's Mathematics for Computer Science textbook, Chapter 1, treats a proof as deductions built from accepted starting points and earlier results. It emphasizes identifying assumptions and explaining what supports each conclusion. Use your course's definitions and allowed results when completing the record.
Write down:
- The domain of each variable.
- What is given or assumed.
- The exact conclusion to establish.
- The proof method, if identified.
- Any definition or earlier theorem invoked.
- Any gap that the slide leaves to the spoken lecture.
A slide that says “clearly” still needs a reason you can explain. If you cannot supply one from the course, mark the step for follow-up.
Use a statement-and-reason ledger
| Step | Statement | Why it follows | Dependency or open question |
|---|---|---|---|
| Start | Assumptions and variable domains | Given in the claim | Record the original slide |
| Definition | Rewrite a term precisely | Course definition | Check introduced variables |
| Deduction | Obtain a new statement | Earlier line, algebra, or permitted theorem | Name what is being used |
| Finish | Connect the result to the claim | Definition or established implication | Confirm the original target was proved |
Do not fill the reason column with “then” or “therefore” alone. Those words announce a deduction without justifying it. Ask what would break if the preceding assumption changed.
For long arguments, group the rows by lemma, case, or induction stage. Keep the connections visible. A compressed slide may be suitable for presentation while your study version needs more detail.
Teaching example: preserve the integer witness
The slide fragment and draft are invented teaching examples, not a real course excerpt, recorded Notoo output, or product test. Consider this elementary claim:
The sum of two odd integers is even.
A plausible draft says, “Odd plus odd is even because 3 + 5 = 8.” That example illustrates the claim but does not establish it for every pair of odd integers.
A complete ledger for the claim is:
| Step | Statement | Reason |
|---|---|---|
| 1 | Let a and b be arbitrary odd integers | We must cover any such pair |
| 2 | a = 2r + 1 and b = 2s + 1, for integers r and s | Definition of an odd integer |
| 3 | a + b = 2r + 1 + 2s + 1 = 2(r + s + 1) | Substitution and algebra |
| 4 | r + s + 1 is an integer | Integers are closed under addition |
| 5 | a + b is even | It is twice an integer, the definition of even |
The important bridge is not merely seeing a factor of 2. The quantity inside the brackets is an integer. If a draft drops that domain, restore it. Also note that this argument proves the stated direction; it does not say that any two integers with an even sum must both be odd.
A counterexample to that different claim is 2 + 4 = 6. The counterexample diagnoses an overextended conclusion; it does not replace the proof above.
Reconstruct the argument without the ledger
Close the proof and write the claim, assumptions, main strategy, and deductions from memory. Then compare your attempt with the course source.
Cornell's study guidance recommends active recall to expose what needs more work. Here, use that principle to locate the first unsupported transition rather than judging your attempt by whether the final answer looks familiar.
Classify the miss:
- Definition gap: you cannot unpack a term.
- Domain gap: you introduced a variable without its required type or range.
- Dependency gap: a step uses an earlier result you cannot state.
- Direction gap: you proved the converse instead of the requested implication.
- Completion gap: the algebra is correct but you did not connect it to the target.
Correct the smallest missing reason and try again in a later session. Copying the entire slide immediately can conceal the exact point that caused trouble.
Adjust the record for different proof methods
For cases, list the cases and why together they cover the possibilities in scope. A correct argument in one case does not finish the others.
For contradiction, distinguish the temporary negation of the claim from the original assumptions. Identify the actual contradiction rather than concluding that a result merely feels unlikely.
For induction, record the starting index, base case, induction hypothesis, and target next step. Check that the transition covers the index range in the theorem. Follow the precise version taught in your course; this checklist is not a substitute for learning the method.
Keep AI notes beside the proof
Notoo's slides-to-notes page describes structured drafts from readable decks and cautions that missing spoken context and difficult visuals need checking. If uploads are permitted, use a draft to organize the topic, then manually verify the symbols, domains, and reasons against the source.
Do not treat a generated explanation as a proof checker. Notoo is not being claimed here to certify validity, find every circular argument, or reconstruct every missing deduction. Flashcards may test a definition or theorem condition; a complete proof still needs connected reasoning.
If your difficulty is choosing and applying an expression, see studying equations in a course PDF. If it is predicting a procedure's state changes, use pseudocode hand tracing. Those are different tasks from establishing a universal claim.
Copy the proof study record
Course / topic / deck version:
Slide or PDF page:
Exact claim and variable domains:
Given assumptions:
Definitions and earlier results allowed:
Proof method:
Statement / reason / dependency for each step:
First gap in my closed-note attempt:
Source used to resolve it:
What would fail if an assumption changed:
Question for the tutor:
Later reconstruction date:
For international students, keep logical connectors beside short plain-English meanings. Practise explaining whether a sentence introduces an assumption, a consequence, or a contradiction. Preserve the course's mathematical meaning when translating.
Start with one short proof
Choose a proof your lecturer has already discussed, make the ledger, and attempt it without the answer. If your course permits it, upload the deck to Notoo for a structured draft to organize beside your own reasoning. Ask about unresolved steps before treating them as learned.