Data Structures & AlgorithmsProving Greedy Correctness

Proving Greedy Algorithm Correctness

LevelIntermediate

Duration75 mins

TopicProving Greedy Correctness

1 / 4

The Challenge of Proving Greedy Works

When Intuition Deceives

Greedy algorithms are seductive. They whisper a simple promise: make the best choice at each step, and you'll reach the best overall solution. The logic seems unassailable—surely, a sequence of optimal local decisions must lead to a globally optimal outcome?

Yet this intuition is treacherous. Greedy algorithms fail far more often than they succeed. The vast majority of optimization problems cannot be solved by greedy approaches, and even for problems where greedy can work, choosing the wrong local criterion leads to spectacularly wrong answers.

This creates a fundamental challenge: How do we distinguish problems where greedy works from those where it doesn't? And when we believe we've found a working greedy strategy, how do we prove—rigorously and convincingly—that it actually produces optimal solutions?

What You Will Learn

By the end of this page, you will understand why proving greedy correctness is fundamentally challenging, recognize the common pitfalls that make greedy proofs difficult, appreciate the difference between intuition and proof, and see why rigorous verification is not academic pedantry but essential engineering practice.

The Allure and Danger of Greedy Algorithms

Greedy algorithms attract us because they embody a profoundly human form of reasoning. When faced with complex decisions, we naturally simplify: What's the best thing I can do right now? This strategy often works well in daily life—pick the shortest checkout line, take the fastest route, choose the most urgent email to answer.

In algorithm design, this translates to a beautifully simple paradigm:

Identify a choice to make (which item to select, which task to schedule, which edge to include)
Commit to the locally optimal choice (the greedy criterion)
Never reconsider (no backtracking, no undoing)
Repeat until done

The appeal is undeniable. Greedy algorithms are typically:

Easy to design — the local choice is often obvious
Easy to implement — simple loops with straightforward logic
Efficient to execute — often O(n log n) or O(n) for sorting then scanning

The Dangerous Assumption

The seductive simplicity of greedy algorithms conceals a dangerous assumption: that no local choice can ever 'paint you into a corner.' Greedy assumes that committing early can never foreclose better options later. This assumption is false for most problems.

Why Greedy Fails So Often

Consider a simple analogy. You're hiking toward a mountain peak in dense fog. At each step, you move toward higher ground—the local optimum. Does this guarantee you reach the highest peak?

Absolutely not. You might climb a lesser hill and become trapped there, unable to descend (that would move away from higher ground!) to reach the true summit beyond.

This is the local optima trap, and it haunts optimization problems. The globally optimal solution often requires temporary sacrifices—accepting locally suboptimal choices—that greedy cannot make because it never looks ahead.

Why Greedy Fails: Common Patterns
Problem Type	Greedy Approach	Why It Fails	Correct Approach
0/1 Knapsack	Select highest value/weight ratio items	May not fully utilize capacity; fractional thinking doesn't apply	Dynamic Programming
Longest Path in Graph	Always move to nearest unvisited node	Local proximity doesn't indicate path contribution	Dynamic Programming or Backtracking
Traveling Salesman	Visit nearest unvisited city	Creates crossings; final return may be very long	DP, Branch & Bound, Approximation
Coin Change (some systems)	Use largest denomination first	May not reach exact change; misses optimal combinations	Dynamic Programming
Minimum Spanning Tree with constraints	Add minimum edge	May violate degree or structural constraints	Specialized algorithms

The Proof Burden: Why Intuition Is Not Enough

Given how frequently greedy fails, any claim that a greedy algorithm works demands proof, not merely intuition. This is not academic rigidity—it's the difference between an algorithm you can trust and one that might fail catastrophically on edge cases you haven't considered.

The Core Question

When we claim a greedy algorithm is correct, we're asserting something profound: For every possible input, the sequence of locally optimal choices produces a globally optimal solution. This is a universal claim covering infinitely many inputs—you cannot verify it by testing.

Consider what a correctness proof must establish:

The greedy choice is safe — Making this choice doesn't eliminate the possibility of reaching an optimal solution
The remaining problem has the same structure — After making the choice, we face a smaller instance of the same problem type
The combined solution is optimal — The greedy choice plus the optimal subsolution equals the optimal total solution

The Induction Connection

Greedy correctness proofs are fundamentally inductive. We show that each greedy choice preserves optimality (inductive step), and that the base case trivially produces an optimal solution. This mirrors how greedy algorithms operate: recursively solving smaller and smaller subproblems.

Why Proofs Are Hard

Proving greedy correctness is challenging for several interconnected reasons:

1. The space of alternatives is vast

To prove greedy optimal, we must argue that no alternative sequence of choices could yield a better solution. But there are typically exponentially many alternatives—we cannot enumerate them all.

2. Interactions are complex

Choices interact across the algorithm's execution. A choice that seems safe in isolation might create problems only apparent later. Proofs must account for these non-local effects.

3. Counterexamples are subtle

When greedy fails, it often fails rarely—on specific input structures that seem unusual but are perfectly valid. Finding these counterexamples requires adversarial thinking.

4. The greedy criterion matters enormously

Two different greedy criteria for the same problem (e.g., "select by value" vs "select by value/weight ratio") may have completely different correctness properties. Proofs are always tied to a specific criterion.

Common Proof Mistakes to Avoid

•Hand-waving 'obvious' claims — Stating 'clearly, this is optimal' without rigorous justification. Obvious claims are where bugs hide.
•Proving feasibility only — Showing greedy produces a solution, not that it produces the optimal solution.
•Circular reasoning — Using 'greedy is optimal' as part of the argument for why greedy is optimal.
•Ignoring edge cases — Proving for 'typical' inputs but missing boundary conditions where greedy fails.
•Confusing heuristic success with optimality — 'It works on all test cases' is not a proof; it's wishful thinking.

A Concrete Failure Case: The Coin Change Problem

To understand why proofs matter, let's examine a case where greedy seems obviously correct but isn't—the Coin Change Problem.

Problem Statement: Given a set of coin denominations and a target amount, find the minimum number of coins needed to make exactly that amount.

The Greedy Approach: Always select the largest coin that doesn't exceed the remaining amount. Repeat until done.

Intuition: Using larger coins first minimizes the number of coins needed. This seems obviously correct.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
def greedy_coin_change(denominations, target):
    """
    Greedy approach: always use the largest coin possible.
    WRONG for many denomination systems!
    """
    denominations = sorted(denominations, reverse=True)  # Largest first
    coins_used = []
    remaining = target
    
    for coin in denominations:
        while remaining >= coin:
            coins_used.append(coin)
            remaining -= coin
    
    if remaining == 0:
        return coins_used
    return None  # Cannot make exact change
 
# US currency: works!
us_coins = [25, 10, 5, 1]
print(f"41 cents with US coins: {greedy_coin_change(us_coins, 41)}")
# Output: [25, 10, 5, 1] - 4 coins, which is optimal
 
# Canonical counterexample: coins = [1, 3, 4], target = 6
bad_coins = [4, 3, 1]
print(f"6 with [1,3,4]: {greedy_coin_change(bad_coins, 6)}")
# Output: [4, 1, 1] - 3 coins
# But optimal: [3, 3] - only 2 coins!

Greedy Fails Here

With denominations [1, 3, 4] and target 6, greedy selects 4 (the largest fitting coin), then is forced to use two 1s, for a total of 3 coins. But the optimal solution uses two 3s—only 2 coins. The 'obvious' greedy approach is wrong.

Why This Matters

The coin change counterexample illustrates a critical lesson: intuition about greedy correctness is unreliable. The greedy approach seems so natural, so obviously right, that many programmers would implement it without question.

But 'seems right' is not 'is right.' Without proof, we cannot distinguish the US coin system (where greedy works) from the [1, 3, 4] system (where it doesn't).

The Mathematical Reason

Greedy works for US coins because the denomination system is canonical—a mathematical property where greedy always succeeds. Not all denomination systems are canonical, and determining canonicity is itself a non-trivial problem.

This is why we need proof techniques. We need systematic methods to determine:

Does greedy work for this specific criterion on this problem?
Can we construct a proof that it works for all inputs?
Or can we find a counterexample showing it fails?

Coin Systems: Where Greedy Works vs Fails
Denomination System	Target	Greedy Result	Optimal Result	Greedy Optimal?
[1, 5, 10, 25]	30	[25, 5]	[25, 5]	✓ Yes
[1, 5, 10, 25]	41	[25, 10, 5, 1]	[25, 10, 5, 1]	✓ Yes
[1, 3, 4]	6	[4, 1, 1]	[3, 3]	✗ No
[1, 5, 6, 10]	12	[10, 1, 1]	[6, 6]	✗ No
[1, 7, 10]	14	[10, 1, 1, 1, 1]	[7, 7]	✗ No
[1, 2, 5]	11	[5, 5, 1]	[5, 2, 2, 2] or [5, 5, 1]	✓ Yes

The Structure of Greedy Correctness Proofs

All rigorous greedy proofs share a common structural template. Understanding this template provides a roadmap for constructing your own proofs and evaluating others.

The Two Pillars of Greedy Correctness

Every greedy proof must establish two properties:

1. Greedy Choice Property There exists an optimal solution that includes the greedy choice. This doesn't mean every optimal solution includes it—just that at least one does. We can safely make the greedy choice without eliminating all optimal solutions.

2. Optimal Substructure After making the greedy choice, the remaining problem is a smaller instance of the same problem, and an optimal solution to the original includes an optimal solution to this subproblem.

The Key Insight

The greedy choice property is where the real work happens. Optimal substructure is usually straightforward to verify once you've shown the greedy choice is safe. Most of our proof techniques focus on demonstrating that the greedy choice doesn't foreclose optimality.

The Proof Template

Most greedy proofs follow this pattern:

Step 1: Define the greedy choice precisely

What exactly does the algorithm select at each step?
What criterion is used to make this selection?

Step 2: Establish the greedy choice property

Take any optimal solution (assume one exists)
Show that this optimal solution can be modified to include the greedy choice
Show that this modification preserves optimality (doesn't increase cost/decrease value)

Step 3: Show optimal substructure

After making the greedy choice, identify the remaining subproblem
Argue that this subproblem has the same structure as the original
Show that the optimal solution to the original = greedy choice + optimal subsolution

Step 4: Conclude by induction

Base case: trivially optimal when problem is empty or has one choice
Inductive step: greedy choice + optimal subsolution = optimal total solution

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
THEOREM: The greedy algorithm G produces an optimal solution for problem P.
 
PROOF:
We proceed by induction on problem size.
 
BASE CASE (size = 0 or 1):
  - [Show trivially optimal, usually empty solution or single choice]
 
INDUCTIVE STEP:
  Assume G produces optimal solutions for all instances of size < n.
  Consider an instance I of size n.
  
  GREEDY CHOICE PROPERTY:
  Let S* be any optimal solution for I.
  Let g be the greedy choice made by G on I.
  
  Case 1: g ∈ S*
    - The optimal solution already includes our greedy choice. Done.
  
  Case 2: g ∉ S*
    - Construct S' from S* by [swapping/replacing] some element with g
    - Show cost(S') ≤ cost(S*) [or value(S') ≥ value(S*)]
    - Therefore S' is also optimal and includes g
  
  OPTIMAL SUBSTRUCTURE:
  After choosing g, the remaining problem I' has size < n.
  By inductive hypothesis, G produces optimal solution for I'.
  The combined solution {g} ∪ (optimal for I') is optimal for I.
 
  Therefore G produces an optimal solution for I.
  
By induction, G produces optimal solutions for all instances.  ∎

Preview: Two Major Proof Techniques

The template above is abstract. In practice, we need concrete techniques for Step 2 (establishing the greedy choice property). Two techniques dominate greedy correctness proofs:

1. Greedy Stays Ahead

This technique shows that at every stage of the algorithm, the greedy solution is at least as good as any other solution at the same stage. If greedy never falls behind, it must be optimal at the end.

This is like watching a race: if Runner A is always at or ahead of everyone else at every checkpoint, Runner A wins. We don't need to analyze alternative strategies—staying ahead at every point guarantees victory.

2. Exchange Argument

This technique starts with any optimal solution and shows that it can be transformed step-by-step into the greedy solution without losing optimality. If we can exchange our way from any optimal solution to the greedy solution, the greedy solution must also be optimal.

This is like showing that any winning lottery ticket can be converted into our ticket without changing the prize—proving our ticket is also a winner.

Greedy Stays Ahead

•Show greedy is always at least as good
•Works by maintaining an invariant
•Often easier for scheduling problems
•Natural when there's a clear measure of 'progress'
•Example: Activity Selection (earliest finish time)

Exchange Argument

•Transform optimal to greedy solution
•Works by showing safe swaps exist
•Often easier for selection problems
•Natural when solutions are sets/sequences
•Example: Huffman Coding, Fractional Knapsack

Upcoming Deep Dives

The next two pages explore each technique in detail with complete worked examples. You'll see how 'Greedy Stays Ahead' proves Activity Selection optimal, and how the Exchange Argument proves Huffman Coding optimal. These are the core tools in your greedy proof toolkit.

When Proof Attempts Reveal Failure

One of the most valuable aspects of attempting correctness proofs is that failed proofs often reveal counterexamples. When you try to construct a proof and get stuck, the place where you're stuck frequently points directly to why the algorithm fails.

The Proof-Failure Feedback Loop

Consider this virtuous cycle:

Propose a greedy strategy for a problem
Attempt to prove it correct using one of our techniques
If the proof works, you have a correct algorithm with formal justification
If the proof fails, ask: What input would violate this claim?
Construct a counterexample exploiting that violation
Either refine the greedy criterion and return to step 2, or recognize greedy won't work and try DP/other approaches

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
"""
Problem: Select maximum-value subset of items with total weight ≤ capacity.
         (This is 0/1 Knapsack)
 
Proposed Greedy: Select items in decreasing order of value/weight ratio.
 
Proof Attempt:
  Claim: The item with highest value/weight ratio must be in optimal solution.
  
  Let's try to prove this...
  
  Consider item x with highest ratio v_x / w_x.
  Suppose optimal solution S* doesn't include x.
  We want to show we can add x to S* or swap something for x.
  
  PROBLEM: Adding x might exceed capacity!
  And if we remove something to make room, we might remove more
  value than x contributes, since fractions aren't allowed.
 
The proof breaks down because:
  1. We can't take fractions of items
  2. Weight constraints create indivisibilities
  3. Optimal packing may not follow ratio ordering
 
Counterexample (from the proof failure):
  Items: A (value=60, weight=10), B (value=100, weight=20), C (value=120, weight=30)
  Capacity: 50
  
  Ratios: A=6.0, B=5.0, C=4.0
  
  Greedy by ratio: Take A (ratio 6.0), Take B (ratio 5.0), weight=30
                    C doesn't fit.
                    Total value = 160
  
  Optimal: Take B + C, weight=50, Total value = 220
  
The counterexample was exactly at the point where the proof broke:
we couldn't swap items freely due to capacity constraints.
"""
 
def knapsack_greedy_by_ratio(items, capacity):
    """items = [(value, weight), ...]  - DOES NOT GIVE OPTIMAL"""
    sorted_items = sorted(items, key=lambda x: x[0]/x[1], reverse=True)
    total_value = 0
    total_weight = 0
    selected = []
    
    for value, weight in sorted_items:
        if total_weight + weight <= capacity:
            selected.append((value, weight))
            total_value += value
            total_weight += weight
    
    return total_value, selected
 
# Demonstrate the failure
items = [(60, 10), (100, 20), (120, 30)]
capacity = 50
print(f"Greedy result: {knapsack_greedy_by_ratio(items, capacity)}")
# Output: (160, [(60, 10), (100, 20)])
# Optimal is 220 with [(100, 20), (120, 30)]

The Value of Failed Proofs

A failed proof is not wasted effort. It tells you exactly where greedy goes wrong for this problem. This insight often leads directly to correct dynamic programming solutions, as the 'stuck point' reveals what state you need to track.

The Practical Importance of Rigor

Some engineers dismiss correctness proofs as academic exercises disconnected from real-world practice. This is a dangerous misconception.

Why Proofs Matter in Production

Consider the consequences of deploying an incorrect greedy algorithm:

Resource allocation systems: Suboptimal allocations waste money continuously
Scheduling systems: Suboptimal schedules delay work, compound over time
Network routing: Suboptimal routes waste bandwidth, increase latency
Compression: Suboptimal encoding increases storage and transmission costs
Financial algorithms: Suboptimal trades lose money directly

Why Proofs Are Practical

•Confidence in edge cases — Production systems see inputs you never tested. Proofs cover all cases, including adversarial ones.
•Documentation of reasoning — Proofs explain why the algorithm works, helping future maintainers understand and modify safely.
•Foundation for optimization — Once you have a correct algorithm, you can optimize implementations knowing the logic is sound.
•Defense against subtle bugs — Greedy algorithms look simple but hide complex failure modes. Proofs expose these.
•Interview and review credibility — Proposing algorithms without justification signals shallow understanding; proofs demonstrate mastery.

The Spectrum of Rigor

In practice, proofs exist on a spectrum:

Formal proof — Complete mathematical argument with all steps justified
Informal proof — Clear argumentation that could be formalized if needed
Proof sketch — Key ideas without full details; 'obvious' steps elided
Intuitive argument — Explains why it 'should' work without rigorous structure
Testing only — No justification; rely on test coverage

Professional practice typically operates at levels 2-3. Formal proofs are for textbooks and verification; informal proofs are for code reviews and documentation. What matters is that you can be rigorous when challenged.

Level 5 is acceptable for heuristics (where optimality isn't claimed) but dangerous for algorithms where greedy correctness is assumed.

Summary: The Challenge of Proving Greedy

We've established why proving greedy correctness is both challenging and essential. Let's consolidate the key insights:

Key Takeaways

•Greedy algorithms fail more often than they succeed — Most optimization problems can't be solved greedily, and choosing the wrong criterion leads to incorrect solutions.
•Intuition about greedy correctness is unreliable — The coin change example shows that 'obviously correct' often isn't.
•Proofs establish universal correctness — Unlike testing, proofs cover all possible inputs including adversarial ones.
•All greedy proofs rely on two pillars — Greedy Choice Property (safe to make this choice) and Optimal Substructure (remaining problem is smaller version of original).
•Two main proof techniques exist — 'Greedy Stays Ahead' and the Exchange Argument, each suited to different problem types.
•Failed proofs are valuable — They reveal why greedy fails and often point directly to counterexamples.
•Rigor has practical value — Proofs provide confidence, documentation, and defense against subtle bugs in production systems.

What's next:

Now that we understand why greedy proofs are challenging and important, we'll explore our first proof technique in depth: the 'Greedy Stays Ahead' argument. This powerful technique will let us rigorously prove that algorithms like Activity Selection are optimal by showing greedy never falls behind any alternative.

Page Complete

You now understand the fundamental challenge of proving greedy algorithms correct. You've seen why intuition fails, how proofs are structured, and why rigorous justification matters. Next, we'll equip you with the first proof technique: Greedy Stays Ahead.

1 / 4

Loading learning content...

Data Structures & AlgorithmsProving Greedy Correctness

Proving Greedy Algorithm Correctness

LevelIntermediate

Duration75 mins

TopicProving Greedy Correctness

1 / 4

The Challenge of Proving Greedy Works

When Intuition Deceives

What You Will Learn

The Allure and Danger of Greedy Algorithms

In algorithm design, this translates to a beautifully simple paradigm:

Identify a choice to make (which item to select, which task to schedule, which edge to include)
Commit to the locally optimal choice (the greedy criterion)
Never reconsider (no backtracking, no undoing)
Repeat until done

The appeal is undeniable. Greedy algorithms are typically:

Easy to design — the local choice is often obvious
Easy to implement — simple loops with straightforward logic
Efficient to execute — often O(n log n) or O(n) for sorting then scanning

The Dangerous Assumption

Why Greedy Fails So Often

Consider a simple analogy. You're hiking toward a mountain peak in dense fog. At each step, you move toward higher ground—the local optimum. Does this guarantee you reach the highest peak?

Absolutely not. You might climb a lesser hill and become trapped there, unable to descend (that would move away from higher ground!) to reach the true summit beyond.

Why Greedy Fails: Common Patterns
Problem Type	Greedy Approach	Why It Fails	Correct Approach
0/1 Knapsack	Select highest value/weight ratio items	May not fully utilize capacity; fractional thinking doesn't apply	Dynamic Programming
Longest Path in Graph	Always move to nearest unvisited node	Local proximity doesn't indicate path contribution	Dynamic Programming or Backtracking
Traveling Salesman	Visit nearest unvisited city	Creates crossings; final return may be very long	DP, Branch & Bound, Approximation
Coin Change (some systems)	Use largest denomination first	May not reach exact change; misses optimal combinations	Dynamic Programming
Minimum Spanning Tree with constraints	Add minimum edge	May violate degree or structural constraints	Specialized algorithms

The Proof Burden: Why Intuition Is Not Enough

The Core Question

Consider what a correctness proof must establish:

The greedy choice is safe — Making this choice doesn't eliminate the possibility of reaching an optimal solution
The remaining problem has the same structure — After making the choice, we face a smaller instance of the same problem type
The combined solution is optimal — The greedy choice plus the optimal subsolution equals the optimal total solution

The Induction Connection

Why Proofs Are Hard

Proving greedy correctness is challenging for several interconnected reasons:

1. The space of alternatives is vast

To prove greedy optimal, we must argue that no alternative sequence of choices could yield a better solution. But there are typically exponentially many alternatives—we cannot enumerate them all.

2. Interactions are complex

Choices interact across the algorithm's execution. A choice that seems safe in isolation might create problems only apparent later. Proofs must account for these non-local effects.

3. Counterexamples are subtle

When greedy fails, it often fails rarely—on specific input structures that seem unusual but are perfectly valid. Finding these counterexamples requires adversarial thinking.

4. The greedy criterion matters enormously

Common Proof Mistakes to Avoid

•Hand-waving 'obvious' claims — Stating 'clearly, this is optimal' without rigorous justification. Obvious claims are where bugs hide.
•Proving feasibility only — Showing greedy produces a solution, not that it produces the optimal solution.
•Circular reasoning — Using 'greedy is optimal' as part of the argument for why greedy is optimal.
•Ignoring edge cases — Proving for 'typical' inputs but missing boundary conditions where greedy fails.
•Confusing heuristic success with optimality — 'It works on all test cases' is not a proof; it's wishful thinking.

A Concrete Failure Case: The Coin Change Problem

To understand why proofs matter, let's examine a case where greedy seems obviously correct but isn't—the Coin Change Problem.

Problem Statement: Given a set of coin denominations and a target amount, find the minimum number of coins needed to make exactly that amount.

The Greedy Approach: Always select the largest coin that doesn't exceed the remaining amount. Repeat until done.

Intuition: Using larger coins first minimizes the number of coins needed. This seems obviously correct.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
def greedy_coin_change(denominations, target):
    """
    Greedy approach: always use the largest coin possible.
    WRONG for many denomination systems!
    """
    denominations = sorted(denominations, reverse=True)  # Largest first
    coins_used = []
    remaining = target
    
    for coin in denominations:
        while remaining >= coin:
            coins_used.append(coin)
            remaining -= coin
    
    if remaining == 0:
        return coins_used
    return None  # Cannot make exact change
 
# US currency: works!
us_coins = [25, 10, 5, 1]
print(f"41 cents with US coins: {greedy_coin_change(us_coins, 41)}")
# Output: [25, 10, 5, 1] - 4 coins, which is optimal
 
# Canonical counterexample: coins = [1, 3, 4], target = 6
bad_coins = [4, 3, 1]
print(f"6 with [1,3,4]: {greedy_coin_change(bad_coins, 6)}")
# Output: [4, 1, 1] - 3 coins
# But optimal: [3, 3] - only 2 coins!

Greedy Fails Here

Why This Matters

But 'seems right' is not 'is right.' Without proof, we cannot distinguish the US coin system (where greedy works) from the [1, 3, 4] system (where it doesn't).

The Mathematical Reason

This is why we need proof techniques. We need systematic methods to determine:

Does greedy work for this specific criterion on this problem?
Can we construct a proof that it works for all inputs?
Or can we find a counterexample showing it fails?

Coin Systems: Where Greedy Works vs Fails
Denomination System	Target	Greedy Result	Optimal Result	Greedy Optimal?
[1, 5, 10, 25]	30	[25, 5]	[25, 5]	✓ Yes
[1, 5, 10, 25]	41	[25, 10, 5, 1]	[25, 10, 5, 1]	✓ Yes
[1, 3, 4]	6	[4, 1, 1]	[3, 3]	✗ No
[1, 5, 6, 10]	12	[10, 1, 1]	[6, 6]	✗ No
[1, 7, 10]	14	[10, 1, 1, 1, 1]	[7, 7]	✗ No
[1, 2, 5]	11	[5, 5, 1]	[5, 2, 2, 2] or [5, 5, 1]	✓ Yes

The Structure of Greedy Correctness Proofs

All rigorous greedy proofs share a common structural template. Understanding this template provides a roadmap for constructing your own proofs and evaluating others.

The Two Pillars of Greedy Correctness

Every greedy proof must establish two properties:

The Key Insight

The Proof Template

Most greedy proofs follow this pattern:

Step 1: Define the greedy choice precisely

What exactly does the algorithm select at each step?
What criterion is used to make this selection?

Step 2: Establish the greedy choice property

Take any optimal solution (assume one exists)
Show that this optimal solution can be modified to include the greedy choice
Show that this modification preserves optimality (doesn't increase cost/decrease value)

Step 3: Show optimal substructure

After making the greedy choice, identify the remaining subproblem
Argue that this subproblem has the same structure as the original
Show that the optimal solution to the original = greedy choice + optimal subsolution

Step 4: Conclude by induction

Base case: trivially optimal when problem is empty or has one choice
Inductive step: greedy choice + optimal subsolution = optimal total solution

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
THEOREM: The greedy algorithm G produces an optimal solution for problem P.
 
PROOF:
We proceed by induction on problem size.
 
BASE CASE (size = 0 or 1):
  - [Show trivially optimal, usually empty solution or single choice]
 
INDUCTIVE STEP:
  Assume G produces optimal solutions for all instances of size < n.
  Consider an instance I of size n.
  
  GREEDY CHOICE PROPERTY:
  Let S* be any optimal solution for I.
  Let g be the greedy choice made by G on I.
  
  Case 1: g ∈ S*
    - The optimal solution already includes our greedy choice. Done.
  
  Case 2: g ∉ S*
    - Construct S' from S* by [swapping/replacing] some element with g
    - Show cost(S') ≤ cost(S*) [or value(S') ≥ value(S*)]
    - Therefore S' is also optimal and includes g
  
  OPTIMAL SUBSTRUCTURE:
  After choosing g, the remaining problem I' has size < n.
  By inductive hypothesis, G produces optimal solution for I'.
  The combined solution {g} ∪ (optimal for I') is optimal for I.
 
  Therefore G produces an optimal solution for I.
  
By induction, G produces optimal solutions for all instances.  ∎

Preview: Two Major Proof Techniques

The template above is abstract. In practice, we need concrete techniques for Step 2 (establishing the greedy choice property). Two techniques dominate greedy correctness proofs:

1. Greedy Stays Ahead

2. Exchange Argument

This is like showing that any winning lottery ticket can be converted into our ticket without changing the prize—proving our ticket is also a winner.

Greedy Stays Ahead

•Show greedy is always at least as good
•Works by maintaining an invariant
•Often easier for scheduling problems
•Natural when there's a clear measure of 'progress'
•Example: Activity Selection (earliest finish time)

Exchange Argument

•Transform optimal to greedy solution
•Works by showing safe swaps exist
•Often easier for selection problems
•Natural when solutions are sets/sequences
•Example: Huffman Coding, Fractional Knapsack

Upcoming Deep Dives

When Proof Attempts Reveal Failure

The Proof-Failure Feedback Loop

Consider this virtuous cycle:

Propose a greedy strategy for a problem
Attempt to prove it correct using one of our techniques
If the proof works, you have a correct algorithm with formal justification
If the proof fails, ask: What input would violate this claim?
Construct a counterexample exploiting that violation
Either refine the greedy criterion and return to step 2, or recognize greedy won't work and try DP/other approaches

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
"""
Problem: Select maximum-value subset of items with total weight ≤ capacity.
         (This is 0/1 Knapsack)
 
Proposed Greedy: Select items in decreasing order of value/weight ratio.
 
Proof Attempt:
  Claim: The item with highest value/weight ratio must be in optimal solution.
  
  Let's try to prove this...
  
  Consider item x with highest ratio v_x / w_x.
  Suppose optimal solution S* doesn't include x.
  We want to show we can add x to S* or swap something for x.
  
  PROBLEM: Adding x might exceed capacity!
  And if we remove something to make room, we might remove more
  value than x contributes, since fractions aren't allowed.
 
The proof breaks down because:
  1. We can't take fractions of items
  2. Weight constraints create indivisibilities
  3. Optimal packing may not follow ratio ordering
 
Counterexample (from the proof failure):
  Items: A (value=60, weight=10), B (value=100, weight=20), C (value=120, weight=30)
  Capacity: 50
  
  Ratios: A=6.0, B=5.0, C=4.0
  
  Greedy by ratio: Take A (ratio 6.0), Take B (ratio 5.0), weight=30
                    C doesn't fit.
                    Total value = 160
  
  Optimal: Take B + C, weight=50, Total value = 220
  
The counterexample was exactly at the point where the proof broke:
we couldn't swap items freely due to capacity constraints.
"""
 
def knapsack_greedy_by_ratio(items, capacity):
    """items = [(value, weight), ...]  - DOES NOT GIVE OPTIMAL"""
    sorted_items = sorted(items, key=lambda x: x[0]/x[1], reverse=True)
    total_value = 0
    total_weight = 0
    selected = []
    
    for value, weight in sorted_items:
        if total_weight + weight <= capacity:
            selected.append((value, weight))
            total_value += value
            total_weight += weight
    
    return total_value, selected
 
# Demonstrate the failure
items = [(60, 10), (100, 20), (120, 30)]
capacity = 50
print(f"Greedy result: {knapsack_greedy_by_ratio(items, capacity)}")
# Output: (160, [(60, 10), (100, 20)])
# Optimal is 220 with [(100, 20), (120, 30)]

The Value of Failed Proofs

The Practical Importance of Rigor

Some engineers dismiss correctness proofs as academic exercises disconnected from real-world practice. This is a dangerous misconception.

Why Proofs Matter in Production

Consider the consequences of deploying an incorrect greedy algorithm:

Resource allocation systems: Suboptimal allocations waste money continuously
Scheduling systems: Suboptimal schedules delay work, compound over time
Network routing: Suboptimal routes waste bandwidth, increase latency
Compression: Suboptimal encoding increases storage and transmission costs
Financial algorithms: Suboptimal trades lose money directly

Why Proofs Are Practical

•Confidence in edge cases — Production systems see inputs you never tested. Proofs cover all cases, including adversarial ones.
•Documentation of reasoning — Proofs explain why the algorithm works, helping future maintainers understand and modify safely.
•Foundation for optimization — Once you have a correct algorithm, you can optimize implementations knowing the logic is sound.
•Defense against subtle bugs — Greedy algorithms look simple but hide complex failure modes. Proofs expose these.
•Interview and review credibility — Proposing algorithms without justification signals shallow understanding; proofs demonstrate mastery.

The Spectrum of Rigor

In practice, proofs exist on a spectrum:

Formal proof — Complete mathematical argument with all steps justified
Informal proof — Clear argumentation that could be formalized if needed
Proof sketch — Key ideas without full details; 'obvious' steps elided
Intuitive argument — Explains why it 'should' work without rigorous structure
Testing only — No justification; rely on test coverage

Level 5 is acceptable for heuristics (where optimality isn't claimed) but dangerous for algorithms where greedy correctness is assumed.

Summary: The Challenge of Proving Greedy

We've established why proving greedy correctness is both challenging and essential. Let's consolidate the key insights:

Key Takeaways

•Greedy algorithms fail more often than they succeed — Most optimization problems can't be solved greedily, and choosing the wrong criterion leads to incorrect solutions.
•Intuition about greedy correctness is unreliable — The coin change example shows that 'obviously correct' often isn't.
•Proofs establish universal correctness — Unlike testing, proofs cover all possible inputs including adversarial ones.
•All greedy proofs rely on two pillars — Greedy Choice Property (safe to make this choice) and Optimal Substructure (remaining problem is smaller version of original).
•Two main proof techniques exist — 'Greedy Stays Ahead' and the Exchange Argument, each suited to different problem types.
•Failed proofs are valuable — They reveal why greedy fails and often point directly to counterexamples.
•Rigor has practical value — Proofs provide confidence, documentation, and defense against subtle bugs in production systems.

What's next:

Page Complete

1 / 4