Tuesday, June 30, 2009

Chapter One: Nico Parks

He looks up at the stars, the shining bright of life.  Only to imagine the world he left almost two years ago.  The darkness still lingers ever so tightly as he approaches the ramp to the underground moon.  Hugging his ghost and walking onward, he still gets the same feeling he felt the first time he walked outside.  Space, the fear of darkness and lifelessness, the silent singing of being alone, he never liked going outside.

 

The teams of five approach the ramped gate that holds the paraterraformed innards of the moon Nona Que.  A large portal like metal door held together by the grounds of the moon.  Helped by large pipes, wires and gears that are punctured straight through the ground forming what looks to be a cybernetic implanted structure.  Pulsating and turning to open up what was the new formed life of this dead star. The gates of life open and present the shining glow of green light fighting to escape the underworld, only to be consumed by the depth of space.  The chaotic particles are once again disregarded by all the men, except one.

 

Before walking in he looks up at the stars once again, to see the shining brightness of life only light years away.  Nico Parks, The Wolf.

Posted by Guardian45 at 23:06:49 | Permalink | No Comments »

Sunday, June 14, 2009

Incident

Start Log [T.10.16.52.1]

Log [1.04 Y.2188]

 

I have had success in recovering past log issues, thankfully.  This is good news, not only am I able to recover the majority of the log within the archive, but the corruption has left little damage to the system itself.  The only drawback is that decrypting corrupted logs are taking much longer than I thought it would and most of my logs are still in the darkness.  On top of that, I need to have my Armor Guard connected to the unit itself if I am able to have any success in recovering the logs.  This causes a problem, and it seems I may only download during my hibernation hours.

 

How I was able to find a solution to the corruption in the first place was almost a fluke of itself.  But I have more important matters to explain, so I may go further in detail about how I was able to recover the system at a later date.  1: For documentation.

 

1: For documentation. I’m still in search of my “John” log.

Let me explain.  Here on Choir we use the word incident to describe a personnel malfunction, i.e. death of an intelligent being.  Whether that malfunction may be an accident or intention, we still refer to it as incident, never a death, murder, rape, suicide, or anything of the like.  

 

When said incident is an accident or intention, the following must be done. 

a.         An analysis on the situation that followed before and after the incident took place.

b.         An autopsy on said “John[s]” or “Jane[s]”.  Even when empirical observation is relevant when said John[s] or Jane[s] became the incident.

c.         Documentation on all following personnel whom witnessed the/an incident.  Documentation pertaining information received and about the witness[es].

d.         All documentation about the incident and John[s] or Jane[s] sent to company headquarters.

e.         Remains sent to closest alliance owned planetary control.

 

From the amount of time I have been on this rock, there has only been one incident.  The incident was soon ruled an accident.  I don’t believe that official statement.

 

The Wolf

End Log [T.10.20.22.10]

Posted by Guardian45 at 06:47:01 | Permalink | No Comments »

Tuesday, June 9, 2009

The Wolf

Start Log [T.2.30.21.12]

Log [1.02 Y.2188]


 

632D[ays] and somehow the past voice logs I documented, fell into a system corruption.  I have spent the last week trying to work out the core memory system within Choir’s AI center that supplies digital space for all the personnel here.  Nothing works on this godforsaken rock and I should have known that from the start.  The Choir is thirty years too old and getting older.  I would have used my own mainframe catalog to chronicle the statements, but working with Chior’s second rate nano-tech leaves flaws with new technology.  I hope in the next few days I can salvage atleast something.

 

In the mean time, I have switched over to my AIAG3 catalog server, and thankfully it has a system link to these new space helmets we use at the dig sites.  The suits we have are new as well, seems human safety is only a priority when it comes to handling Magnolic Metals we mine down here.  Unfortunately for us, when accidents arise, it costs more to fix the mistakes than it is to replace the work, especially when you hit gold.  So to kill two birds with one stone and to keep personnel malfunctions low, all personnel are issued new standard ghost suits each year.  Not to keep us safe though…

 

It seems I’m at my level now.  When I get back to the Choir I will need to document past statements if my effort to free any corrupt logs is not plausible.
The Wolf

End Log [T.2.32.32.5]

Posted by Guardian45 at 09:04:20 | Permalink | No Comments »