The product dims and blurs behind one oversized command palette; the typed query is the headline and chunky 3D keycaps get struck on the kick drum. Acme Pulse lives inside the palette, so finding the anomaly and deciding what to do are the same two keystrokes.
The K keycap slams down on the first kick (translateY 10 px, 80 ms) and the palette springs up from 96 % scale; the query types one letter per 1/8 note and the “38 results” counter ticks up on beat 4.
On the drop the ↵ key strikes and the top result expands in place (height 82→170 px, back.out 1.4, 0.3 s) into the Acme Pulse lockup; two teal rings radiate outward from the palette on the next two beats while the app behind stays blurred.
The anomaly row drops in from the top of the list (y −24→0, power3.out 0.25 s) and the result rows FLIP-re-rank beneath it; the selection bar slides onto “Roll back” and the coral ⌥ R keycaps strike together on the snare. The human's keystroke is the decision.
The palette shrinks to three rows (FLIP, 0.25 s power3.out) as the tagline types in above it; the coral ↵ keycap is struck on the last downbeat and holds, glowing, under the “Start free” row.
Why: the command palette is the most recognisable “power user” gesture in modern software, and it makes human control literal: the anomaly only goes away when a key is pressed. Readable at feed size because it is one centred box. Risk: reads developer-only; soften with plain-language result rows and keep the typed query short.
Adapt to your product: replace the result rows with your own objects and actions, and let your product's name be the scope chip; the final ↵ is always your CTA.
References: Superhuman — building a remarkable command palette · Linear — behind the design refresh