Show & tell — a 30-second screening workflow over 13,963+ live Polymarket markets, zero login.

I built polyscope because I kept doing the same thing manually: open Polymarket, hunt for markets that moved, cross-check volume, and try to spot the ones quietly crashing. That's a scanning problem, and a single scannable page beats clicking through hundreds of market pages.

Here's the actual workflow I run, in order:

1. Open Movers first (not Volume).
The 24h movers list surfaces where conviction changed today. High-volume markets are often already-priced consensus — the edge is in the delta, not the size. (There's an open Ideas thread debating Movers-first vs Volume-first — #3 — curious where you land.)

2. Sanity-check against Volume leaders.
A big mover on thin volume is noise. A big mover that also shows up in volume leaders is a real repricing. The two lists together are the filter.

3. Scan the Crash Signal column.
This flags markets dropping fast enough to look like a resolution-driven collapse vs. normal chop. Methodology + the 73% figure are written up in #2 — I'd rather you poke holes in the method than take the number on faith.

4. Filter by category.
Politics behaves nothing like crypto behaves nothing like sports. Filtering by category before reading movers keeps you from comparing a 4% sports drift against a 40% crypto unwind.

The point: it's free, no wallet, no login, no email gate — https://luciferforge.github.io/polyscope/. The whole thing is a static read over public market data.

What I want from you:

• What's the first column your eye goes to, and is it on the page yet?
• Is there a screening view you run mentally that the tool doesn't capture?
• For the crash signal specifically — what would make you trust it (or what's the obvious false-positive case I'm missing)?

Drop a workflow below. The roadmap is genuinely being seeded from these threads.