[themedic274]

Looks like Genus decided to do it!

Quote:

The reinforcements arrived hours ago, and we are just waiting for the re-phasement to complete. I am personally glad that Genus Orein complied with the request. The reinforcements are now set in position and should be ready whenever the re-phasement completes. I have confirmed that we should be ready to extract the Jhuku from the planet before it is sent back to the future.

Has anyone asked Skyfall about the boy?

[Lystella]

punxtr wrote:

Quote: RESPONSE: Apologies for the delayed update broadcast. I my services were temporarily shut as I was asked to perform a complex operation. My databases are offline as well, and thus no logs were created yesterday January 27, 2012. ???

While I'm not sure, it could have been my inquiry regarding whether the origin of the beacon signals was the escape pod itself (which was answered minutes before the log notification). Apologies to everyone if that is the case.

LAINSY/RUBY wrote:

RESPONSE: I wasn't able to determine if the pod was the one giving the beacon signals. However, the beacons signals are not detected to be on the coordinates of the pod. It was only when your companions have told me where to look that I have found the pod.

I also asked about the current date of the pod and received this twelve hours before the notification.

LAINSY/RUBY wrote:

RESPONSE: Current date on the pod retrieved is 01/27/2495

Again, apologies if either one (or both?) of those inquiries had resulted in a complex operation. I will refrain from making inquiries during the duration of the active logging for time being.

[punxtr]

Quote:

RESPONSE: Apologies for the delayed update broadcast. I my services were temporarily shut as I was asked to perform a complex operation. My databases are offline as well, and thus no logs were created yesterday January 27, 2012.

???

[godder]

I'll send an email to Genus letting him know that reinforcements are on the way and that the Oriru Serku are going to retrieve Jhuku themselves if he can't get him in the next 24 hours. I'll let him know about the boy in the pod as well.

[themedic274]

New email from Skyfall!

Quote:

So how are things progressing? I hope you have done your best in getting Genus Orein to release Afyg. In roughly 24 hours, the reinforcements that will be sent by Oriru Serku will arrive and should be able to proceed with getting back to it's timeline. If they try to fight, they will be able to fend them off. I am not fully aware if you are in contact with Genus Orein, but in the past few days is seems he has not anything to prepare in releasing the planet. I hope you understand how grave things can get if the criminal get's loose. Additionally, while we do not mandate you to let Genus Orein retrieve the Jhuku by himself, I am sure Oriru Serku would be in gratitude if Genus Orein does it himself. Nonetheless, the reinforcements to arrive will be able to do the task if he's not up to that. Atthe very least, I ask that he release the planet. Of course, we should be able to find a way around his de-phasement, but I assume you agree that it would be best if he did it himself. I am trying to be much kinder to show you that despite the Oriru Serku being persistent about the safety of the Jhuku, we are much open to consider things. Let's just say, disregard the need to take out FAILTECH. You see, originally, FAILTECH had never existed in the first six iterations. Thus only with the tampering of this iteration that FAILTECH existed. Now, Oriru Serku has become open to it's existence in hopes that this HUGE difference could show solutions to problems that has long stopped us from progressing forward in fear of the inevitable catastrophe. And to re-affirm what I ask you to do, you need to get Genus Orein to release the planet Afyg. He may or may not cooperate, we will find a way around and get what we need. Personally, I'd want him to do it as a positive show for the Oriru Serku,

[zeighy]

Maybe you could ask what's the current time on the pod's systems... Maybe, we'll know how long it has been since it was ejected...

[Lystella]

I was considering Jhuku as well.

LAINSY/RUBY wrote:

Pod Ejection Date=01/18/2495

In terms of speculating what might have happened, is it likely the pod was ejected before it traveled through time, or ejected on the 18th of 2012 with the systems not taking the time jump into account?

[punxtr]

Quote:

Active Log number 01202015-457826A : CLASSIFIED ENTRY Updated by: LAINSY/RUBY Tier 2 access was successful. Updated by FAILTECH/548342 Thanks to LAINSY, we were able to determine the boy's condition. It seems safe to take him out of stasis, we will do that, however I am just awaiting confirmation from superiors before proceeding. I still wonder where this boy has come from. He is related to FAILTECH, somehow, and being form the future is still quite vague. LAINSY wasn't able to find much useful information about the pod's origin in the pod's Tier 2 systems. Only thing we got from there is access to the computer's subsystems for the stasis and other systems that take care of the pod's functions. --- Active Log number 12292011-008234A : AI Self Development Phase 3 NO UPDATES --- Active Log number 01232012-700381A : HTR Agent Live Subject Test Update by: FAILTECH/167299 It is quite heartbreaking that we have failed. A small oversight that we might have not anticipated is that there a variation in the reaction time of the agent to different kinds of tissues. Additionally, it seems the cancelling agent does not work if the HTR agent has adjusted for a particular DNA pattern. For now, we have sent the subject to cryo and will work on the cancelling agent. The HTR Agent proves to be successful, however, the cancelling agent needs to be worked on. --- Active Log number 01232012-701112A : CLASSIFIED ENTRY NO UPDATES

So, they messed up on the HTR, and the being from the pod is indeed a boy. Jhuku?

[Tharol]

Same here agent likes check.

[zeighy]

Hope that guy with the HTR agent is doing good....

[Lystella]

Log update:

Quote:

Active Log number 01202015-457826A : CLASSIFIED ENTRY Updated by: LAINSY/RUBY Attempts to access to Tier 2 of the pod's computer system has failed. I have already requested assistance. Updated by FAILTECH/548342 We can't completely determine the condition of the boy, but scans indicate that there are no immediate threats if he is released from stasis. We will wait until LAINSY gather's more information once she's able to access the Tier 2 of the pod's computer. --- Active Log number 12292011-008234A : AI Self Development Phase 3 NO UPDATES --- Active Log number 01232012-700381A : HTR Agent Live Subject Test Update by: FAILTECH/283310 !!IMPORTANT HTR Agent has now shown signs of activity on the subject. Ms. Sunday is current away and as second in command, I am taking the privilage to report that HTR Agent shows positive signs of activity. Despite the extended period of no activity on the subject, it has now began to show repairs on the tissues of the subject. I suspect that the agent, as it was introduced externally instead of being injected or ingested, took a while to access any DNA record of how to repair the tissues. It seems at current rate, the HTR Agent will be able to repair the subject's external parts in 5 to 7 hours. We are still unaware if the agent is performing any internal repairs. We will initiate scans once we deem it is safer to perform the scans. Right now, we just want to let the agent perform what it needs to without any external factors keyed in. We can only confirm the success of the test once scan has been performed. Cancelling Agent will only be introduced once we want to halt the regeneration process or if anything untowards occurs. Update by: FAILTECH/167299 I wasn't there when the agent started to show signs of activity, however it seems the activity has now drastically slowed down. It is very promising. We have now administered the cancelling agent so that the HTR Agent will halt, however, we still see no signs of reaction or halting. We will wait for a few hours to confirm if it indeed halted. --- Active Log number 01232012-701112A : CLASSIFIED ENTRY Update by: FAILTECH/017224 Batch failure. Improvements neccessary.

[duke9509]

Quote:

Active Log Number 01232012-700381A has just been updated with an entry marked as IMPORTANT Update by: FAILTECH/283310 HTR Agent has now shown signs of activity on the subject. Ms. Sunday is current away and as second in command, I am taking the privilage to report that HTR Agent shows positive signs of activity. Despite the extended period of no activity on the subject, it has now began to show repairs on the tissues of the subject. I suspect that the agent, as it was introduced externally instead of being injected or ingested, took a while to access any DNA record of how to repair the tissues. It seems at current rate, the HTR Agent will be able to repair the subject's external parts in 5 to 7 hours. We are still unaware if the agent is performing any internal repairs. We will initiate scans once we deem it is safer to perform the scans. Right now, we just want to let the agent perform what it needs to without any external factors keyed in. We can only confirm the success of the test once scan has been performed. Cancelling Agent will only be introduced once we want to halt the regeneration process or if anything untowards occurs.

[Lystella]

Me too.

Daniel Miller wrote:

the HTR Agent is still unstable at it's current state and the human tissue regeneration is uncontrollable once started.

Cancer or maybe some more limbs, livers, and spleens to poke at for tests? *cringes*

EDIT: Log updates!

Quote:

01202012-457826A : CLASSIFIED ENTRY (Escape pod) 12292011-008234A : AI Self Development Phase 3 01232012-700381A : HTR Agent Live Subject Test 01232012-701112A : CLASSIFIED ENTRY

Quote:

Please note that we only send one consolidated email update daily for active log updates. We only send immediate updates if an entry has been updated marked with "IMPORTANT", "URGENT", or something similar. --- Active Log number 01202015-457826A : CLASSIFIED ENTRY Updated by: LAINSY/RUBY Object retrieval successful as requested by the expert. It has been put under isolation in flight bay 1. Further inspections has been performed. I was able to access it's computer and details as follows: Manufacturing date=06/24/2488; Registration name=FAILTECH/VALESCO; Pod Ejection Date=01/18/2495; Passenger On Board=NO INFORMATION; Ejection Reason=MANUAL Updated by FAILTECH/548342 At LAINSY's instructions, we have checked carefully checked the person on board the pod. She says the pod is an escape pod, so in my theory the person on board has probably escaped from an exploding ship or so. Due to the nature of the operations of this company, it is quite feasable that this is something beyond our current time. It is quite evident on the information on it's computer that it IS from the future. However, it travelling back in time is still a "HOW". The passenger on board is a young boy, roughly 3-5 years old. It seems to be on stasis, which is quite reasonable if you are escaping in space. The time before you can be located on such as small vessle can take time given that space is wide and nearly infinite. We haven't released him, yet. We still have to confirm he will be ok once ejected and that there are no hazards of releasing him. LAINSY still has to access tier 2 of the computer systems to retrieve more information. --- Active Log number 12292011-008234A : AI Self Development Phase 3 NO UPDATES --- Active Log number 01232012-700381A : HTR Agent Live Subject Test Updated by: FAILTECH/167299 Day 0 of the test. Although the subject is doubtful of the result, I feel confident we can have the agent controlled this time. Lab simulations and clean room experiments has shown that the HTR agent can be cancelled by the cancelling agent we were able to produce recently. Subject is a medical patient who is suffering from FOURTH DEGREE BURNS, from the recent take down on the Colorado Facility. He is nearly clinging on to his life, and hopefully with the help of the HTR Agent, we can regenerate and fix him. We have briefed him of the consequences of the failure of this test, and he was still willing. However, like stated he is doubtful of the result. Subject has been sprayed with the HTR Agent, however, no immediate signs of activity has been recorded. Will update the log if anything happens. --- Active Log number 01232012-701112A : CLASSIFIED ENTRY NO UPDATES

[godder]

I signed up for the updates as well. Hmmm. Interesting. I'd hate to be the test subject for that!

"Hold out your hand." *WHACK*
"AAAAAGH!!!"
"Ok, now lets see if this batch works this time."

[Lystella]

I'm worried about how the HTR log and classified log below it appear to have the same date.

*signs up for the rest*