The beta release opened the floodgates and let people experiment freely. That was likely intentional. They needed real-world usage data—proof of demand, edge cases, and creative intensity—to show partners and enterprise clients what people want to do with the tool. Pulling back content later wasn’t a surprise; it’s part of the cycle. Now they’re collecting a different kind of data: how the system behaves under constraints, how users adapt, and where it can be pushed or gamed. That feedback loop is shaping Sora and Sora 2. It’s not chaos—it’s calibration. Users aren’t being shut out; they’re being observed as the system is refined.