ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Large Hadron Collider - Kweejaq, The Council & The Fate Of The Planet

Updated on November 27, 2009

Kweejaq stood in front of the holographic real time representations of the Galactic Council and took a deep breath. He usually avoided breathing deeply whenever he was on Qanran as the atmosphere always had that horrible residual methane smell of immature planets. However, this was only the seventh time in his career he had to face the Galactic Council to make this particular type of recommendation and he was naturally wary and saddened: The magnitude of his conclusion weighed as heavily on his twelve legs as Qanran's oppressive gravity.

The Galactic Council's holographs formed a semi circle in front of him, in consideration that his species only had forward vision. The Presiding Moderator of the Galactic Council addressed Kweejaq and instructed him to begin the presentation with the characteristic courtesy of the inhabitants of his planet. His telepathic waves were savory and rounded with just a tinge of the ultraviolet... a formal etiquette verging on the aristocratic.

Kweejaq began in the conventional manner with a telepathic broadcast of the background of the case with regards to planet S-J74T59K03X18Z23-A, the primary S in the Standard Galactic Catalog indicating that it was a planet observed to have sapient life and the last -A indicating that it was of primary interest to the Galactic Council as it was in the foremost critical stage of sapient technological evolution. Planets were only named in the Standard Galactic Catalog once its inhabitants were deemed to be potential future members of the Galactic Unity.

S-J74T59K03X18Z23-A was just another planet that would never get its formal name. Its inhabitants called it Earth, but then again, most hominids called the planet where they evolved Earth no matter where in the galaxy they were: There were literally thousands of Earths. Fortunately the Galactic Catalog's formal name was always unique like the one for his home planet: Xyhiakha, which in the language of his ancestors meant Shining Metallic Cloud.

Planet S-J74T59K03X18Z23-B was upgraded to the critical -A stage sixty-five of the planet's years ago when its sole predominant technological species of land dwelling hominids achieved their first nuclear fission explosion. Galactic Council Observers were immediately dispatched and began their task of data collection, triggering the normal and inevitable viewings and interactions. Again in the conventional pattern, the hominids largely dismissed these identifications in their skies as the illusions or outright delusions of their more addled members.

The case of this particular planet was exacerbated by the presence of another, much more advanced sapient species of liquid dwelling ungulates who had long ago outgrown technology as well as survival on the harsh surface of their world. Fortunately these ungulates had worked in unison with the Galactic Council and soon transferred their communal consciousness off the planet to allow it to continue unhindered.

From the point of first fission, the pattern followed by these hominids did not deviate significantly from the established norm of technological species. Soon they progressed to fusion explosions as well as the utilization of fission for energy generation purposes. The Galactic Council Observer Task Force's data and sample collection continued with no resistance as the hominids' technological development curve followed strictly conventional patterns based on their anatomy and lifespan. As their typical but fundamental misunderstanding of quantum states of matter, energy and time continued, also in the conventional pattern, they built the typical particle accelerator to attempt to observe the Primal Particle: which they called the Higgs Boson.

Continued In: Large Hadron Collider - Kweejaq, The Council & The Fate Of The Planet: Part II

Back To Start

Comments

    0 of 8192 characters used
    Post Comment

    No comments yet.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://hubpages.com/privacy-policy#gdpr

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)