Starter track
Step 1 of 60 / 6 completeAlgorithms and Search Foundations
Next after this: Binary Search / Halving the Search Space.
This concept is the track start.
Concept module
Watch sorting as visible work on a live list so input order, comparisons, and writes stay concrete instead of collapsing into one final answer.
Interactive lab
Loading the live simulation bench.
Progress
Not startedMastery: NewLocal-firstStart exploring and Open Model Lab will keep this concept's progress on this browser first. Challenge mode has 1 compact task ready. 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 1 of 60 / 6 completeNext after this: Binary Search / Halving the Search Space.
This concept is the track start.
Why it behaves this way
Sorting should feel like a visible process, not a before-and-after jump. This bench keeps the live list, the active comparisons, and the running costs together so each algorithm leaves a readable trace.
The point is not to memorize a complexity table first. The point is to watch the same sorted output arrive through different local decisions, and to see why input order changes the story.
Key ideas
Frozen walkthrough
Premium unlocks saved study tools, exact-state sharing, and the richer review surfaces that support this guided flow.
View plansBubble
shuffled
1. Name the live setup
2. Read the visible cost
3. Read how much disorder is left
Current trade-off read
Common misconception
If two algorithms end with the same sorted list, they must have behaved in basically the same way.
The same final answer can hide very different step patterns and costs.
This is why the list view and the counters stay visible together.
Mini challenge
Make a prediction before you reveal the next step.
Check your reasoning against the live bench.
Quick test
Reasoning
Question 1 of 2
Use the live bench to test the result before moving on.
Accessibility
The simulation shows an array of bars. The active interval, settled region, and pointer markers show what the current sorting algorithm is doing, while a readout card reports comparisons, writes, and remaining disorder.
Graph summary
One graph tracks comparisons and writes over time. A second graph tracks inversions remaining versus settled items, and a third graph shows the fraction of disorder left.
Read next
Open the next concept, route, or track only when you want the current model to widen into a larger branch.
Keep an ordered list, the low-mid-high markers, and the shrinking interval visible together so binary search feels visual instead of procedural.
Keep one live graph, one local neighborhood, and one frontier cue visible together so graph structure feels readable before traversal rules get formal.
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.