Layer depth rule
A newly discovered neighbor sits one edge deeper than the node that found it.
Concept module
Keep the queue frontier, visited count, and graph layers visible together so breadth-first search reads as a layered process instead of a procedure list.
The simulation shows one labeled graph with the current node, the queue frontier, and the visited nodes colored differently so the BFS layers stay readable. A readout card reports the traversal mode, current node, frontier size, visited count, and target, while a cue panel shows the frontier order and the current neighbor list. Breadth-first search is running on the layered campus graph from A toward H. The start node is waiting on the frontier. The frontier currently holds 1 node, and 0 nodes have already been visited.
Interactive lab
Graph traversal bench
Keep one live graph, the current frontier, and the visited state visible together so breadth-first and depth-first search read like different process choices on the same structure.
Controls
Swap among a few bounded graph scenes without leaving the shared bench.
Choose where the traversal begins.
Mark the node the search is trying to reach.
Compare queue-like breadth-first expansion with stack-like depth-first branching.
More tools
Secondary controls, alternate presets, and less-used toggles stay nearby without crowding the main bench.
More presets
Presets
Time
0.00 s / 20.3 sLivePause to inspect a specific moment, then step or scrub through it.Predict -> manipulate -> observe
Keep the active prompt next to the controls so each change has an immediate visible consequence.
Graphs
Switch graph views without breaking the live stage and time link.
Visited nodes versus frontier size
Watch how many nodes have already been expanded while the waiting frontier grows or shrinks.
Equation map
Select a symbol to highlight the matching control and the graph or overlay it most directly changes.
Switches among the bounded graph scenes on the same traversal bench.
Equations in play
Choose an equation to sync the active symbol, control highlight, and related graph mapping.
More tools
Detailed noticing prompts, guided overlays, and challenge tasks stay available without taking over the main bench.
What to notice
Keep the graph and one traversal graph visible together.
Guided overlays
Focus one overlay at a time to see what it represents and what to notice in the live motion.
Overlay focus
Keep the current node's neighbor list visible.
What to notice
Why it matters
It keeps breadth-first search tied to real graph structure instead of to a slogan about breadth.
Layer depth rule
A newly discovered neighbor sits one edge deeper than the node that found it.
Queue frontier update
Breadth-first search removes the oldest frontier node, then adds its new neighbors to the back.
Progress
Not startedMastery: NewLocal-firstStart exploring and Open Model Lab will keep this concept's progress on this browser first. No finished quick test, solved challenge, or completion mark is saved yet.
Try this setup
Jump to a named bench state or copy the one you are looking at now. Shared links reopen the same controls, graph, overlays, and compare context.
Saved setups
Premium keeps named exact-state study setups in your account while stable concept links stay public below.
Checking saved setup access.
This concept can keep using stable links while the saved-setups capability resolves for this browser.
Copy current setup
Stable concept and section links stay public below while exact-state setup sharing stays behind premium.
Stable links
Starter track
Step 4 of 60 / 6 completeEarlier steps still set up Breadth-First Search and Layered Frontiers.
Previous step: Graph Representation and Adjacency Intuition.
Short explanation
Breadth-first search keeps the frontier organized like a queue. The oldest claimed node gets expanded next, so the search spreads outward in visible layers instead of diving down one branch immediately.
On this bench the graph, the queue frontier, and the visited count stay coupled. That makes the layered shape of BFS honest: nearby nodes get settled first because the queue keeps earlier discoveries ahead of later ones.
Key ideas
Worked example
Live worked examples are available on Premium. You can still read the full frozen walkthrough on the free tier.
View plansLayered campus
A
B then C
1. Read the first layer
2. Keep the queue order honest
3. Read what that means
BFS layer read
Common misconception
Breadth-first search just means moving around the page in a wide-looking pattern.
The important rule is not the drawing. The important rule is that the oldest claimed node leaves the frontier next.
That queue rule is what makes BFS settle the graph layer by layer.
Mini challenge
Prediction prompt
Check your reasoning
Quick test
Reasoning
Question 1 of 2
Choose one answer to reveal feedback, then test the idea in the live system if a guided example is available.
Accessible description
The simulation shows one labeled graph with the current node, the queue frontier, and the visited nodes colored differently so the BFS layers stay readable.
A readout card reports the traversal mode, current node, frontier size, visited count, and target, while a cue panel shows the frontier order and the current neighbor list.
Graph summary
One graph tracks visited nodes against frontier size, a second tracks current depth against the deepest claimed depth, and a third compares new discoveries with repeat skips.
Together they show how breadth-first search widens and then settles the graph layer by layer.
Keep the queue frontier and the graph layers in view
These suggestions come from the concept registry, so the reason label reflects either curated guidance or the fallback progression logic.
Keep the stack frontier, current depth, and branch order visible together so depth-first search feels like disciplined backtracking instead of random wandering.
Keep repeat skips, waiting frontier nodes, and already-expanded nodes visible together so cycle handling feels like honest bookkeeping on one graph bench.
Keep one live graph, one local neighborhood, and one frontier cue visible together so graph structure feels readable before traversal rules get formal.