Put your hand on CHEW's real requirement chain.
Every barrier below is a real requirement from CHEW's rules engine, seeded from a real illustrative starting state. Flip any lock and watch CHEW respond honestly — this is a sandbox for exploring the actual chain, not a prediction about you, and nothing you do here is saved.
Real conditions, hand-toggled — never saved, never guessed.
Every barrier is a real row from transition_requirements, and each one starts
exactly where CHEW's real rules engine says this illustrative scenario actually stands
today — some already open, most not. Flipping a lock only changes what's shown on
your screen; it never calls CHEW's real completion path and never touches the database, so
experimenting here can't corrupt this demo for the next visitor. Where a barrier connects
to a real capability in CHEW's registry, that connection — and whether a provider is
actually active for it — is shown honestly, the same live data the Network Room and
Opportunity Radar read from.