Investigation Log // Origin File

THE
INVESTIGATION

DropDex began with one question: why do certain drops hit harder than others? The archive exists to document the answer.

Case File 001

The question would not leave.

There was no plan to build an archive. Only a pattern that kept repeating: certain drops created an instant reaction. Not just loudness. Not just popularity. Something in the build, the release, the weight, the texture, and the timing seemed to make a crowd respond all at once.

DropDex is the result of following that question into data.

The Archivist

Someone had to start measuring.

The Archivist is not trying to declare the final answer on bass music. The role is simpler: document the drops, preserve the evidence, question the results, and keep expanding the archive.

The rankings are not treated as permanent truth. They are a record of the model, the dataset, and the current state of the investigation.

Investigation Logs

Field notes from the archive.

Observations, anomalies, rankings, artist fingerprints, and discoveries from the growing DropDex dataset.

Log 001 // Origin File

Where's the Drop?

The Kai Wachi build that started the question behind DropDex: why do certain drops hit harder than others?

Read Log
Log 002 // Finding

The Excision Production Pattern

Early archive results suggest a difference between raw power and production dominance.

Coming Soon
Log 003 // Artist Fingerprint

The Rise of Crankdat

A look at how a new artist entered the archive and climbed rapidly into the top rankings.

Coming Soon
Enter the archive. Investigate Drops Review Research