Filesize Desc -

One day, the Indexer glitched. A massive data-leak began to purge the largest files first. The merchant princes, so heavy with their own importance, were the easiest targets. As their 20TB files were shredded, they plummeted down the rankings.

: Start with a compelling character like Kael who has a clear goal (survival) and a major obstacle (the Indexer). Filesize DESC

Kael watched as the world inverted. In a world sorted by Filesize DESC , being small was usually a death sentence. But as the "heavies" were deleted, the Indexer struggled to find a new "top." One day, the Indexer glitched

Kael looked at his 45 KB file. It wasn't much, but it was stable . It was clean. It was efficient. While the giants collapsed under the weight of their own uncompressed vanity, Kael and the other "low-res" citizens were the only ones left standing. For the first time in history, the Indexer reached the bottom of the list and found that the smallest files were the only ones that still made sense. As their 20TB files were shredded, they plummeted

Every citizen was a walking collection of data. Your status, your housing, and your very right to breathe were determined by the sheer volume of your "Soul-File." The Great Indexer sat at the city's peak, constantly running the sort command. If you were at the top of the list—a bloated 20-terabyte merchant prince—you lived in the clouds. If you were a 2-kilobyte street urchin, you lived in the gutters, literal fragments of a person.

: Ensure a clear beginning (the city's rules), middle (the data leak), and end (the resolution of the sort).