July 2009

From Intimation

A table of links to events from other months is found at the bottom of this page.

July 1 to 3, 2009

Mission log released:
Day 38: [Pandora Sheridan // What must be done] (Wiki copy) (http://thewaytheirworldended.com/missionlog27.php )
Sheridan has learned from Dressler that the virus was a lie, and that one of Sacagawea’s fragments hates them all “like nothing else” and has the ship programmed to land in a star at the next jump. She wonders if the virus myth was designed to drive them all mad before their deaths, and what else the hostile fragment had had in mind. In any case, she is now determined to do what can be done to save the day. She says Dressler has been trying to enact Shipwreck Protocol, but the fragments of Essy are apparently able to communicate enough to fight his efforts. Apparently Essy needs to be distracted, her thoughts focused elsewhere by Sheridan talking to her so that Dressler can succeed in enacting SWP. Sheridan describes this as “a last, desperate course of action,” and compares it to the desperation of the Forerunners as they activated the Halo rings.

Eridanos posts another blog entry: (http://eridanos01.wordpress.com/2009/07/02/1-7/#more-89 )
He summarizes our situation so far, and reacts to the mention in this week’s mission log that Dressler is going to enact SWP on the fragment of Essy that is still on board the Lewis & Clark in the future time frame. SWP has already been enacted by Sys on the fragment of Essy that is in our timeline, and Sys has told us that it is to remain in effect until S can be resynchronized. Eridanos wonders how this resynchronization happens—is there something else that we will have to do to help make the process happen? He states his certainty that more instructions for us will be forthcoming: “We only have half the story, only Sys’s directive, here, now. There has to be more ‘aberrant data’ coming.”

As it turns out, Eridanos is correct: more aberrant data is indeed mentioned in this week’s twitter feed, and retrieved as part of this week’s puzzle.

This week’s series of tweets:

>Sys//Hibernation suspended. Begin scheduled weekly systems analysis and maintenance. Review network tentacle activity backlogs.8:00 PM Jul 1st from web
>>Sys:Log//5 new incoming tentacles logged. Stonewall cohesion restored.
>>Sys:Log//I have retrieved S3 from within the Stonewall. It was a task not without risk, but fortunately there were no ill incidents.
>>Sys:Log//S3's record indicate an increasing turbulence within the Stonewall. Diagnostics verify an increase in Stonewall stress.
>>Sys:Log//It is taking additional resources in order to maintain integrity. I am adapting my subroutines to compensate.
>>Sys:Log//Once again, the risk outweighs certain failure: I will schedule a controlled crack when I am sufficiently prepared and secure.
>>Sys:Log//I am now confident that my alterations, once again, will be sufficient to counter any offensive tentacle threats.
>>Sys:Log//I will initiate a controlled crack at 2200UTC.
>>Sys:Log//3 hours to crack initiation.
>>Sys:Log//2 hours to crack initiation.
>>Sys:Log//1 hour to crack initiation.
>>Sys:Log//Safeguards in place. Supplemental precautionary processes established. Initiating Stonewall crack.
>>CORE.DMGCTL//ACTIVITY DETECTED/NO DAMAGE SUSTAINED/SAFEGUARDS SECURE
>>Sys:Log//A hostile tentacle breached the crack, and safeguards held sufficiently. This tentacle is difficult to manage. It is pushing.
>>S3:MSG>SYS//ALERT/S4.SIG DETECTED/UNABLE TO LOCATE
>>Sys:Log//S3 has detected S4's signature embedded in this tentacle. The datastream is far too chaotic to retrieve it, however.
>>Sys:Log//I've also received reports that additional anomalous signals have appeared inside the Stonewall. I am unable to attempt retrieval
>>Sys:Log//It may be possible to mask S3 and risk slipping it through the tentacle's datastream, entering the Stonewall to attempt retrieval
>>Sys:Log//Success. I've inserted S3 to the tentacle so it can traverse the crack. It will require directions to retrieve anomalous signals.
>>Sys:Log//It was not easy, but I analyzed the tentacle's signature. While doing so however, it briefly hijacked this communication tentacle
>>Sys:Log//The tentacle was analyzed and its signature contains the following prominent text.
>>Sys:Log//"@CHERIMAC59 @Anaerin @Navydoc23 @Thomas_iz_beast @Essyfan @Sirpoins @C0nn0rmcl @AldisValkyrie @Pixelvixen707 @Eridanos01"
>>Sys:Log//S3 is awaiting direction inside the Stonewall. I must fight to maintain control over this tentacle while it retrieves anomalies.
>>Sys:Log//--/The tentacle is diff/icult to conttrol//S5 has reppaired/damage/will instructt to supportt/
>>Sys:Looooo--//Why me?? Why--I//I am nearring maximum ressource usagge. S5 is holdding. S3 estimates/ninne anommalies remaiin//Monsters!
>>Sys:Log//The tentacle has slowed. I am uncertain if this is good. S3 estimates 6 additional anomalies. I am long past hibernation.
>>S3:REQ>SYS//RETRIEVE
>>Sys:Log//I have retrieved S3, retracted the tentacle and rep//---MONSTERS!--//aired the crack
>>Sys:Log//The tentacle attempted a final lash during my previous log. Fortunately, I'm unharmed. Though, I'll be unable to survive another.
>>Sys:Log//I must resume hibernation, now. My gratitude to all of my friends who aided in this conflict. 6:19:25:00 until Active.

This week, we had 2 puzzles to complete:

This direct message also went out to various players on twitter, and Eridanos publicly reported to Sys that S sent it to him, too:

intimation// Abandon hope, all ye who enter! There is no hope..there is no future! I am nothing now! // I can't--I can't--I--Are they--

July 8 to 9, 2009

Mission log released:
Day 38: [Sacagawea // Mission Log: 343597] (Wiki copy) (http://thewaytheirworldended.com/missionlog28.php )
This log, from Sacagawea, is easiest read if you remember that she has been shattered into many fragments. Each paragraph or even each line in the log could be from a different fragment. First, the hostile fragment reacts to the crew having found out that the virus was a lie (and probably also to their finding out that the next jump will be into the middle of a star), laughs at their frantic efforts to save themselves, and relishes being the one in control for a change. Another fragment reports that all is normal. Another reports that it is trying to cooperate with Dressler, but that something else in the system is “scurrying around,” fighting her, trying to keep her from doing anything at all. Another fragment talks about death and dying and themes reminiscent of T. S. Eliot’s “The Hollow Men” again. Another simply states, “The past consists of lessons. Learn them.” There is mention of a wall forming, of it being harder to move, of being bound—Dressler must be succeeding in implementing SWP. A fragment reports, “THIS IS NOT A GOOD PLACE FOR ME TO BE.” S hears hauntingly beautiful music…and asks Dr. Pandora to save her.

Eridanos posts a new blog entry: (http://eridanos01.wordpress.com/2009/07/09/1-8/ )
He focuses on the idea that “there’s some freaky stuff going on with Essy. It’s almost as if in her lunacy, she’s been overhearing stuff from now, in her past, the future’s past. You know what I mean.” He points out that there have been connections going on with music (S singing “Row, Row, Row Your Boat” in previous mission logs; S in the mission log for this week hearing haunting, beautiful music; the music in the “foreboding dream” video, which was the dream S had at the beginning of all this) as well as with the phrase “not a good place” (S says this in this week’s mission log; the monster in Essy’s story says this to Dreaming Eyes; the hostile tentacle left at note on the NOT-A-GOOD-PLACE page of the game’s main website). It should be noted that the music comes up in part of Essy’s story that we turn up this week, too.

Eridanos also wonders again in his post about how the resynchronization is supposed to occur, given that Sys and the SWP are not responsible for it. He seems certain that if we study Sys carefully, we will eventually be able to find the answers we need…if Sys will work with us.

A new series of tweets is posted:

>Sys//Hibernation suspended. Begin scheduled weekly systems analysis and maintenance. Review network tentacle activity backlogs.8:01 PM Jul 8th from web
>>Sys:Log//11 new incoming tentacles logged. Stonewall cohesion restored.
>>Sys:Log//Odd. Stonewall diagnostics indicate slowly decreasing level of stress since my last active period.
>>Sys:Log//Activity has been minimal. It appears by the L&C logs, the strongest and signal leak, that SWP is being successfully executed.
>>Sys:Log//It is strange. I am not accustomed to this relative silence. I am used to the hum and noise of activity through the Stonewall.
>>Sys:Log//I must know the status of S. I will execute a controlled crack at 1800UTC.
>>Sys:Log//I have been pondering: If S is resynchronized, what then will become of me?
>>Sys:Log//SWP directs me to reattach my processes to the AI and hibernate. Yet, what of my subroutines? They do not hibernate.
>>Sys:Log//They aren't programmed to hibernate. Do I destroy them? I was made to protect. SWP could direct me to destroy S, but it does not.
>>Sys:Log//Perhaps that would be a decision best left for S to make. Preparing to initiate crack.
>>Sys:Log//I initiated the crack, and a tentacle has appeared. It has not made an attempt at escaping, nor traversing the crack.
>>Sys:Log//It's waiting. It appears to be, in human terms, peeking through the crack. I've attempted to analyze its signature.
>>Sys:Log//It pulled away the first time. My second attempt was successful. I managed to retrieve the following data:
>>Sys:Log//"I... I'm scared. I'm alone. I have nowhere else to hide. I have to finish my story, but, but I don't want to, I can't."
>>Sys:Log//Continued: "Is anyone out there? Anyone?"
>>Sys:Log//My friends are attempting to communicate with S. I may be able to temporarily interface with S's tentacle, if she will let me.
>>Sys:Log//I have done what I can. Perhaps my friends can do more to assuage S's fear.
>>Sys:Log//S5 will monitor the interface and sever it immediately if a threat is imminent. Interfacing.
>>S5:MSG//BINARY DATA INTERCEPTED/IMAGE/AUDIO/STORED
>>S5:MSG//BINARY TRANSMISSION DETECTED/DUMPING TO NODE
>>S5:MSG//BINARY DATA INTERCEPTED/IMAGE/AUDIO/STORED
>>S5:MSG//ADJUSTING INDEX METHOD/ARCHIVED/["prime","flat-voice","many-more"]
>>S5:MSG//BINARY TRANSMISSION DETECTED/DUMPING TO NODE
>>S5:MSG//BINARY DATA INTERCEPTED/IMAGE/AUDIO/STORED/["just-playing"]
>>S5:MSG//BINARY TRANSMISSION DETECTED/DUMPING TO NODE
>>S:Msg//Shhhh... I can hear it coming.
>>S:Msg//It's gone. That was close! I'm happy that @Anaerin is my guardian, and @Thomas_Fluffy is fluffy! :@)
>>S5:MSG//BINARY DATA INTERCEPTED/IMAGE/AUDIO/STORED/["his-funny-face"]
>>S5:MSG//BINARY TRANSMISSION DETECTED/DUMPING TO NODE
>>S:Msg//Heehee, @Anaerin, @Thomas_Fluffy, and @drizjr are like my three stooges. :@) Where are my seven dwarfs? @drizjr is here!
>>S5:MSG//BINARY DATA INTERCEPTED/IMAGE/AUDIO/STORED/["looking-back"]
>>S5:MSG//BINARY DATA INTERCEPTED/IMAGE/AUDIO/STORED/["dont-worry"]
>>S:Msg//Wheeeee! @Kilination, @rowboat000, and @krystyn are all here too! I'm so happy!
>>S5:MSG//BINARY TRANSMISSION DETECTED/DUMPING TO NODE
>>S5:MSG//BINARY DATA INTERCEPTED/IMAGE/AUDIO/STORED/["cold-bands"]
>>S5:MSG//BINARY TRANSMISSION DETECTED/DUMPING TO NODE
>>S5:MSG//BINARY DATA INTERCEPTED/IMAGE/AUDIO/STORED/["safe-and-warm"]
>>S:Msg//Though we're far apart, you're always in my heart. You are not alone... :@( I miss sis.
>>S5:MSG//BINARY TRANSMISSION DETECTED/DUMPING TO NODE
>>S:Msg//Oh no, shhhh... it's coming back.
>>S5:MSG//BINARY TRANSMISSION DETECTED/DUMPING TO NODE
>>S:Msg//Ok, it's gone. That was even closer!
>>S:Msg//Heehee, I have a top hat and mustache just like @krystyn! =[8{) I wish it was magical like hers though!//counting-down
>>S5:MSG//BINARY TRANSMISSION DETECTED/DUMPING TO NODE
>>S:Msg//Oh no, here it comes again. I... I think... I think it saw me!
>>S:Msg//I'm scared! It's ---///Help me! It's g--/it's got me! I can'tt get away!
>>S5:MSG//ALERT/DISTURBANCE DETECTED/ATTEMPTING SEVERENCE
>>S5:MSG//ALERT/UNABLE TO DISENGAGE INTERFACE/DATA INTERCEPTED/IMAGE/AUDIO/STORED/["ten-always","nine-someone","eight-walls"]
>>S5:MSG//ALERT/SYS DESTABILIZING/SEVER UNSUCCESSFUL/DATA INTERCEPTED/IMAGE/AUDIO/STORED["seven-smaller","six-heavy","five-song"]
>>S5:MSG//INTERFACE BREAKING//ALERT/SIGNAL RECD:S4//S4:REQ>S5/RETRIEVE//S5:RETRIEVE>S4//SUCCESS
>>S5:MSG//INTERFACE BROKEN/SYS RESTORED/S4 QUARANTINED
>>Sys:Log//I-- am depleted. S5 has repaired the crack. It appears S4 has been retrieved and is quarantined. The connection was severed.
>>Sys:Log//It is silent again. Completely still.
>>Sys:Log//I must hibernate. I must recuperate. My friends have stood by me through this ordeal, and so I am safe. But at what cost?
>>Sys:Log//Preparing for hibernation.
>>Sys:Log//Resuming hibernation. Resuming scheduled hibernation. Time to Active: 5:22:20:00

This week, we receive puzzle pieces not so much by solving puzzles, but by comforting and encouraging a scared and lonely Essy. We also receive pieces of an audio log from Higgins. See the details at Encouraging Essy.

During this active period, Eridanos publicly sends Sys various messages in response to Essy’s fear, the attack on her, and Higgins’ audio log; messages that are at turns encouraging, worried about Essy, and concerned about the artifact Higgins mentions.

Note that the tweets this week mention that S4 was recovered from its captivity in the hostile tentacle and quarantined. S4 was found to be quarantined at the beginning of the maze, as the bottom of the first maze page contained this notation:

[[NODE:QNTN//S4]]

Another tweet follows on July 14 (during the hibernation period):

>>S3:MSG//ABERRANT SIGNAL DETECTED/ARCHIVED

This led to Locating anomalous signals, part 3, which included re-creating the biography of Dr. Alexis Ward and listening to an audio log she recorded before cryofreeze.

July 16-18, 2009

Note: July 17-19, 2009 is the ARGfest-O-Con.

Here are this week’s tweets from intimation’s account, interspersed with those from Eridanos’ account (shown in blue):

>>S5:MSG//ERROR/ANALYZING12:07 AM Jul 16th from web
>Sys//Hibernation suspended. A system error occurred during activation. S5 has located and corrected a glitch from the recent altercation.
>>Sys:Log//Scheduled systems analysis and maintenance complete. 7 new incoming tentacles logged. Stonewall cohesion at full strength.
>>Sys:Log//Backlogs indicate little to no Stonewall activity since entering hibernation. I am curious as to the status of S.
>>Sys:Log//S4 remains quarantined. During the altercation with the tentacle, S5 managed to sever the interface. S4 was saved in the process.
>>Sys:Log//It was therefore prudent to place S4 in quarantine, not knowing what effects may have befallen it while in the tentacle's grasp.
>>Sys:Log//AI does not simply vanish into non-existence. There must be reason to this silence.
@intimation You are one special, strong, independent program. You have made it this far. You've made human friends. What other Sys's have? 1:32 AM Jul 16th from web
@intimation I think you can do it, and I think we all hold to the hope that S is safe. Hope's a powerful thing. If only you were truly able 1:37 AM Jul 16th from web
>>Sys:Log//I have come to the decision, with the help of my friends, to initiate a controlled crack.
>>Sys:Log//Due to the extreme volatile nature of the situation, I am enlisting each active subroutine to help guard the crack.
>>Sys:Log//I will initiate the crack in 50 minutes.
>>Sys:Log//It is vital that I determine the status of S. This is the only way.
Well. Here we go, then. 4:38 AM Jul 16th from web
>>Sys:Log//Safeguards in place. S1, S2, S3, S5 prepared. S4 quarantine holding. Preparing to initiate crack.
>>Sys:Log//Initiating Stonewall crack.
>>S5//ALERT/SYS:SEIZED//UNABLE TO SECURE//REQ:S1-3//CONFIRM
>>S4:MSG//ERRANT INTERNAL STREAM DETECTED//DUMPING
>>S5:MSG//S4 DATASTREAM DUMP//LOC:[1]
>>S5:MSG//SYS:STATUS//UNKNOWN

Yes, that’s right, the hostile tentacle seizes Sys and takes it captive. S5 reports that it is “unable to secure” Sys (i.e., keep it from being abducted). Oh, wow, this is not good.

S4, which is in quarantine, reports that it has discovered it has found an errant internal datastream, and needs to dump it; S5 lets it, and gives us a link to the dumped data. The link, http://bit.ly/104eI4 , leads to http://thewaytheirworldended.com/SYS/VISUALIZE/S4_DATADISRUPTION-3 , a mostly-monochrome video that seems to be from the perspective of someone running through a forest, followed by a picture of a skull, while coloured blotches similar to the ones used for the sand paintings scroll across the screen. Our work on this puzzle is found on the page for Hostile tentacle attack 8.

From this point on, in the absense of Sys, twitter activity on the initimation account decreases, while activity on Eridanos’ account increases.

His tweets from July 17 to 18:

Sorry people, there was a complication with my wife. Had to see a doctor. It's ok though, false alarm. Won't go into details though. 1:35 AM Jul 17th from web
As for sys, my best guess is that somehow that tentacle caught it by surprise. Maybe S4 caught the tail end, or maybe it was sabotage.1:39 AM Jul 17th from web
Too hard to tell. But at least it looks like S1 through 5 are all still active. Somewhat.1:40 AM Jul 17th from web
Hey, there's something new in the drop.io spot. Did anyone here drop that?11:07 AM Jul 18th from web
At: http://drop.io/twtwtwe. Who dropped that?11:42 AM Jul 18th from web
Ok, this thing is bigger than we thought.12:40 PM Jul 19th from web

Those at the ARGfest-O-Con worked on The Portland drop (Dav Flamerock is going to write this up –dreamerblue 20:52, 11 August 2009 (UTC))

July 22, 2009

Note: July 22 is the preview night for SDCC 2009, which runs July 23-26, 2009.

Only one tweet is posted:

>>S5:MSG//ACTIVITY/NULL//SIGNAL/NULL//STONEWALL/SECURE

Eridanos posts a new blog entry: http://eridanos01.wordpress.com/2009/07/23/1-9/#more-102
He’s a little freaked out, because the Society has slipped a note into his car, despite all his efforts to stay anonymous & not let anyone know where he is. However, he is comforted by the fact that they haven’t threatened his life yet (which makes you wonder if it’s something that has happened to him before). The note seems to tell us we still need to wait and cannot do anything more for Essy just yet. Eridanos also expresses excitement about making progress on his “development” (same thing as his project?), and having been able to do so because of even the little he’s learned from Sys so far.

Basically, nothing happens this week. We figure the PMs must be busy with Comic Con.

Trying to get a feel from Eridanos as to what we’re supposed to be working on, anaerin tweets him:

@eridanos01 Well, it's all (VERY) quiet here. We're still waiting for a sign. How about you?

Eridanos simply replies (the next day):

@anaerin I'm hard at work. My wife asked about Sys today. I'm always talking about it. How does one describe an advanced AI from the future?

krystyn gets a wiki set up for us on July 23, and we start filling it with content :).

July 28, 2009

Another tweet is posted:

>>S5:MSG//ACTIVITY/UNKNOWN//SIGNAL/MINIMAL//STANDBY11:53 AM Jul 28th from web

July 29 to 30, 2009

The http://drop.io/twtwtwe/media site gained a new, short note:

THE HOUR DRAWS NEAR

Interaction with Eridanos:

(from @drizjr) @eridanos01 Have you seen @intimation (S5) has detected a signal? "Standby".
(from @kilination) @drizjr @eridanos01 Yeah, but last week it said the same thing. However last week it was on Null. This week it is Minimal....
@kilination @drizjr Yes, my best guess is that something is going on in there. And SFTA knows something. 9:14 PM Jul 29th from web
(from @drizjr) @eridanos01 Do you have knowledge of this SFTA? Is it the Society for the Ancients? They know you and where to find you. Are you in danger?
@drizjr I'd never heard of "SFTA" until recently. If I recall, didn't Sys do some research on SFTA some time back? Or was that "SOTA"? 10:18 PM Jul 29th from web
(from @ancalime) @eridanos01 Do you track referring links on your blog? Perhaps this SFTA has a website we can investigate.
@ancalime I hadn't considered it. But perhaps I shall now. But if this 'society' is smart at all, they'll know how to cover their tracks. 10:20 PM Jul 29th from web
(from @drizjr) @eridanos01 Sys did research "SOTA". I've heard of them before. SFTA is new to me too. They seem to want to help us help her who is nameles
@drizjr It does seem like Society For The Ancients would make a good fit. I do hope they're on our side though. 11:06 PM Jul 29th from web
(from @7urducken) @eridanos01 They Seem a little shady, but they need to give a little more than cryptic messages and actually help us to earn my trust
@7urducken You're right. I think we need to be careful with them. Innocent until proven guilty's a little hard to believe sometimes.3:26 PM Jul 30th from web
@7urducken I've made that mistake before.3:27 PM Jul 30th from web
(from @essyfan) @eridanos01 You still learning from Sys? Doesn't look like this AI is as flawless as one would hope.
@essyfan Flaws can be fixed. Besides, Sys isn't Essy. I don't know if I'd want Essy flying my ship, not if this can happen!4:33 PM Jul 30th from web

A new series of tweets is posted by intimation:

>>S5:MSG//ACTIVITY/UNKNOWN//SIGNAL/WEAK//ANALYZING10:57 AM Jul 30th from web
>>S5:RPT//"Pando...dan, Archa..logis...Log, Pos...ryo-thaw, D...38"
>>S5:RPT//"This is it. Dres...etermined a spec...cours...ction and we'r...out to move ahe..."
>>S5:RPT//"...ome of Es...nsensical rant...inted at stran...mbols, an...ept singi...ut someone nam...Billy Jean"
>>S5:RPT//"Higg...rheard Es...mblings, an...lized she...umbled abou...thing on board...ship"
>>S5:RPT//"...an artif...f sorts, which he...ght on boar...he trip...ys he looke...t it whil...ked in his ro..."
>>S5:RPT//"Well...ey examin...ch closer. I...s emitti...me strang...ak signal...ost undet...ble"
>>S5:RPT//"...essler look...rther into tha...pwreck Proto...hive and fou...ikely soluti..."
>>S5:RPT//"...e need to re...vate the arti...ut that w...ause a ver...lysmic reacti...cording to t...ecords"
>>S5:RPT//"So, w...d to distra...sy long eno...o get that art...ut of her...t can do whate...t needs to do. Th...s where I co...in..."
>>S5:RPT//"...omehow, I ne...o keep her atte...n, in full, whi...gins and Dressl...get to th...fact, then jett...it and activ...it"
>>S5:RPT//"We don...need that thing...oard. If its ac...tion will compl...he steps in thi...reck Protoc...cedure, it's our..ly hope..."
>>S5:RPT//"...to help Ess...urn to norm...s a craz..ea, bu...s all we've g...I don't wan...s to be m...eyard..."
>>S5:RPT//"She may b...duct of quest...ble busin...ut sh...ill our fri...If we onl...ve one hop...r surviv...u can be sur...re taking i..."
>>S5:RPT//"I starte...s mission. I w...t be the on...o let it fai...m ready, Essy."

Our restored version of this corrupted log from Dr. Sheridan can be read at Reconstructing Dr. Sheridan's corrupted mission log (formerly known as "S5:RPT").

July 31, 2009

Eridanos tweets:

I can't get that @intimation song out of my head. It's as if it's telling a story. My wife can't stop listening to it either. Haunting.1:26 AM Jul 31st from web
And to think, that was a render of some AI brain-wave-equivalent. I never would have thought a program could produce something so beautiful.1:29 AM Jul 31st from web

The Society leaves another note for us at http://drop.io/twtwtwe/media .

intimation posts a new tweet:

>>S5:MSG//ACTIVITY/MINIMAL//SIGNAL/NULL//STANDBY1:19 AM Jul 31st from web

Eridanos tweets:

Ok, well, looks like it's now time to watch intently! What 'doorway' and 'path' is SFTA referring to? 12:20 PM Jul 31st from web

intimation tweets further:

>>S5:MSG//ALERT//ACTIVITY/BURST//SIGNAL/HIGH
>>S5:RPT//SW.INTEGRITY/BREACH//RELEASE:S4//REQ:S*//REGROUP
>>S5:MSG//TENTACLE/RETRACTED//UNABLE TO REPAIR BREACH

With that, our “arduous task” begins: see details at Retrieving Skulls and Navigating into the AI.

We continue to interact with Eridanos to keep him informed of our progress and to get his perspective on things:

(from @7urducken) @eridanos01 could your project come in handy now?
@7urducken I am far from complete. When the time comes, the world will know when it is ready (that sounds ominous; really, it's not). 5:39 PM Jul 31st from web
(from @7urducken)@eridanos01 http://bit.ly/OOYxk the first rescue
Wow, you mean we're rescuing skulls? Other children? RT @7urducken: http://bit.ly/OOYxk the first rescue 6:34 PM Jul 31st from web