Skip to content

Bridges / Articulation / BCC Ladder

This ladder should make low-link feel like one reusable family, not three unrelated graph tricks.

Who This Is For

Use this lane if:

  • "critical road" and "critical city" still feel like different algorithms
  • you know DFS, but tin / low still feels slippery
  • bridge trees or block-cut trees seem magical instead of structural

This lane is intentionally staged:

  • one flagship bridge rep in-repo
  • one exact starter
  • strong compare points back to traversal, trees, and SCC boundaries

Warm-Up

  • DFS tree
  • entry times
  • back edges to ancestors

Target skill:

  • explain what low[v] means in words before writing code

Core

  • Necessary Roads
  • bridge test low[child] > tin[parent]
  • articulation test low[child] >= tin[parent]
  • root special case

Target skill:

  • move from one DFS invariant to critical-edge / critical-vertex output cleanly

Stretch

Target skill:

  • know when plain bridge/articulation is enough, and when the task really wants a block-cut or bridge-tree reduction

Retrieval Layer

Repo Anchors And Compare Points

The strongest in-repo loop here is:

  1. learn the tin / low invariant from the topic page
  2. solve or revisit Necessary Roads as the clean bridge rep
  3. reopen the Low-Link hot sheet until the bridge/articulation inequalities are automatic
  4. then move to Necessary Cities and Forbidden Cities

Exit Criteria

You are ready to move on when:

  • you can explain low[v] without formula-chasing
  • you no longer mix up > and >=
  • you remember the root articulation rule automatically
  • you can say whether the next structure should be a bridge tree or a block-cut tree

External Practice