We've been waiting to reveal very crucial information for a few months now. Recently we've learned about the potential discovery of a 10th planet in the solar system. Turns out, we've been sitting on a hunk of information.

Signals!

As you know, our eyes pick up any signal between 380 to 700 nanometers (it's literally just how our eyes see). Our eyes are engineered to only detect these subset of signals we termed as the visible spectrum. Many equipment are able to detect other signal lengths.

We've built a robot that hunts down origins of various signals. The robot started with 10 nanometers and analyzed all readings for significance. Suddenly our hearts stopped when we've heard the robot's signal absorbing a ton of signals coming from one spot at around 1 millimeter of signal length. Luckily we've built a 5G tower nearby to broadcast the data.

I couldn't believe my eyes when I heard that signal coming in from the radio.

Identification!

We've made a visual representation of the sky. Just as before, a huge valley was made in our model aligning with the robots signal. This angle perfectly aligns with the inclination projections of the 10th planet. With all the proof needed to prove the presence and position of the 10th planet, we've began writing our scientific papers on the matter.

Publish?

We waited to publish it. A huge argument erupted in our PR department, many researchers was afraid of how the American public would react. We don't know what is on the planet, the millimeter signal could've been a defensive shield or a cloak device around the planet. Anything is possible when working with the possibility of aliens.

Sitting on that information for a while was a bad idea. A known hacking group found a crack in our database and published the article for themselves. It's difficult trying to prove valuable research was stolen from an otherwise trusted and reputable organization; however, we have to fight the controversy and reveal bad actors in the research industry.

No user information was revealed in this database breach. Not like we would say.