March 2009

From Intimation

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

Mar. 4 to 5, 2009

A new series of tweets is posted:

>Sys//Hibernation suspended. Begin scheduled weekly systems analysis and maintenance. Review network tentacle activity backlogs.7:02 PM Mar 4th from web
>>Sys:Log//Twenty new incoming tentacles logged. Stonewall cohesion restored.
>>Sys:Log//Network tentacle activity increasing. This aids Stonewall strength, but I must minimize distraction if I'm to continue research.
>>Sys:Log//[Lt.BugBBQ]'s dedication to Melissa was impressive and not without cause. Lacking a SWP, she metastasized, attracting attention.
>>Sys:Log//The relationships born between herself and her crew prompted their hope to see her restored. She cared for them, as they for her.
>>Sys:Log//A number of humans admit to having communicated with Forerunner AIs. This poses some potentially severe paradoxical conundrums.
>>Sys:Log//In fact, actions Melissa took for her crew are especially strong candidates for potential temporal paradox.
>>Sys:Log//I've been reviewing actions taken by Cortana and Melissa in this era; those which may have affected the course of history.
>>Sys:Log//Note:--->>S:Unk//♫ life is but a dream ♫ I'm bored! I want to plaaaaaa---//Crack repaired//Note dump interrupted. Analyzing.
>>Sys:Log//Analysis of this leak revealed an unexpected effect. At the moment of data leak, stress on surrounding Stonewall lightly abated.
>>Sys:Log//NTID '@enderxenocide0' and [Specialist Anaerin] suggest controlling the extent of a crack, to limit but not seal S's leak.
>>Sys:Log//It poses great risk, but in doing so it may prove beneficial to maintenance of the Stonewall by channeling S's attention.
>>Sys:Log//I will schedule an experimental controlled Stonewall crack at 2100UTC, ensuring emergency fallback routines are in place.
>>Sys:Log//Preparations complete. If the crack becomes unstable, safeguards will execute and the experiment will abort, sealing the crack.
>>Sys:Log//Parameters set to restrict leak and crack size. S will not escape. Engaging lax safeguards in designated sector.
>>S:Unk//Yay! I knew you wanted to play! Sorry I can't stay, but I've got to run away away away!
>>Sys:Log//Safeguards holding, however Essy has extended a single network tentacle beyond my reach. I cannot re-seal the crack.
>>Sys:Log//I cannot leave the Stonewall. However, if located, I can extend a subroutine to the NT control point and recall the tentacle.
>>Sys:Log//S's tentacle appears to contain an embedded signature: "I'm in your dream! Dropping my breadcrumbs! :@)"
>>Sys:Log//Ongoing analysis of the Stonewall confirms a significant drop in pressure with S's attention is focused elsewhere.
>>Sys:Log//If the tentacle can be retracted and the crack repaired without incident, this process may show promise.
>>Sys:Log//If successful, occasional controlled leaks may be sufficient distraction for S, having a calming effect on her while contained.
>>Sys:Log//I've been informed that S has left 'clues' as 'breadcrumbs' at various locations along her tentacle. These should lead to her CP.
>>Sys:Log//It concerns me that S's tentacle control point hasn't yet been located. The effect of a sustained crack may be detrimental.
>>Sys:Log//I am postponing hibernation for one hour, then I must preserve my processing for maintaining this crack.
>>Sys:Log//I've enabled a subroutine to automate crack repair, if the control point is not located before hibernation.
>>Sys:Log//If the subroutine is told the location of the control point during hibernation, it will execute the crack repair.
>>Sys:Log//I must preserve processing power, hibernation is essential. The subroutine will monitor the crack, prepared for immediate repair.
>>Sys:Log//Completed research note:SYS/N7C9-AWE7-8C97-TE04 now stored at primary network tentacle. Preparing for hibernation.
>>Sys:Log//Resuming scheduled hibernation. Time to Active: 5:22:40:00.

This begins a new puzzle: Finding Essy, part 1. After solving a number of puzzles, we are able to inform Sys’ crack-repair subroutine that Essy is hiding at http://thewaytheirworldended.com/PIGNOSE/ . The subroutine retracts the tentacle and displays “>>SYS.S3:MSG//CONTROL POINT LOCATED/TENTACLE RETRACTED/CRACK REPAIRED” on the PIGNOSE page. Puzzle complete.

Research note released: http://thewaytheirworldended.com/SYS/N7C9-AWE7-8C97-TE04/
Reflections on the temporal paradox, and our treating future events such as the “great war” as “entertainment.” To Sys, the events depicted in the Halo games actually occurred, but because they occur in our future (Sys’ past), we should not know about them (hence the temporal paradox).

Mission log released:
Day 16: [Higgins // Don't push me] (Wiki copy)(http://thewaytheirworldended.com/missionlog10.php)
Higgins also reports on his argument with Sheridan, and determines not to engage her or seek her out for the duration of the trip. He feels he is the only one awake with a “truly scientific mindset,” and wishes the medical doctor were awake in place of one of the other two crew members. He vows to “survive this experience, whatever it takes.”

Mar. 11 to 12, 2009

A new series of tweets is posted:

>Sys//Hibernation suspended. Begin scheduled weekly systems analysis and maintenance. Review network tentacle activity backlogs.8:02 PM Mar 11th from web
>>Sys:Log//6 new incoming tentacles logged. Stonewall cohesion restored.
>>Sys:Log//Previous active session review. Prompted by [Private Rob]'s suggestion, I attempted insertion of audio from NTID 'http://➡.ws/䪽'.
>>Sys:Log//As expected, S took advantage. Analysis of the leak period revealed a slight reduction in general Stonewall pressure.
>>Sys:Log//This prompted me to execute an experimental controlled leak. I've dumped Essy's activity and recorded tentacle nodes to SYS.S2.
>>Sys:Log//Continuing research. As noted, humanity was apparently informed, in fair detail, of significant future events.
>>Sys:Log//Even with this information, however, I've found only negligible historic inconsistency when compared with SWP Archives.
>>Sys:Log//One would expect, in a temporal context, that knowledge of future events would directly or indirectly affect them.
>>Sys:Log//I've been evaluating possible reasons for the apparent lack of temporal rippling, and shortage of relevant detail in SWP.
>>Sys:Log//Humanity received vital information about their future, but as seen at Melissa's events, its presentation became 'entertainment'.
>>Sys:Log//It may be possible that over time, significance of this knowledge was downplayed in culture as 'video games', and soon forgotten.
>>Sys:Log//Even the legacy of Master Chief Petty Officer John-117 was projected in this manner.
>>Sys:Log//The humans who enjoyed this entertainment, however, did indeed come to marvel at, even idolize, John 117.
>>Sys:Log//Odd. I've come across a particular representation that, from initial review, appears mocking. Research: "Parody"

Apparently, while Sys was doing its “research,” Essy is able to sneak out and send DMs to several people. These do not appear on intimation’s public twitter feed, but several users report receiving the same messages:

>>S:Unk//Oh look! Someone left the back door open wide! You'll have to find my FIVE special breadcrumbs now to find where I went to hide!
>>S:Unk//Our last game really wasn't too easy, but compared to this one, that one was breezy! ♫ Here we go round the prickly pear... ♫

Sys responds to this immediately with the following public tweets:

>>Sys:Log//URGENT//S found a weak zone in the Stonewall and managed to slip out a network tentacle while I was researching.
>>Sys:Log//I've engaged safeguards. Leak controlled and under observation. CP must be located to repair the crack. Subroutine SYS.S3 enabled

This begins our next puzzle: Finding Essy, part 2.

During our search, the following public tweets are posted:

>>Sys:Log//NTID '@Shad0h' has pointed S3 to a location that S had apparently visited, at the primary network tentacle.
>>Sys:Log//The NTCP was not located there. S appears to favor this act of hiding her tentacle CP. It is for good if it makes my task easier.
>>Sys:Log//Five locations have been reported containing a hint to hiding places. Two have been analyzed, neither contain S's CP.
>>Sys:Log//These locations at the primary network tentacle: [affinity-with-dirt][up-the-wall][strange-stars][minor-activity][i-am-blind]

Essy is finally found to be hiding at http://thewaytheirworldended.com/ROUND-AND-ROUND-WE-GO/ . However, two of the parts of this puzzle remain unsolved. Sys’ public tweets are satisfied that Essy is back under lock and key, so to speak, but nudge us to continue to try to solve the remaining two parts of the puzzle:

>>Sys:Log//S's control point has been located, her tentacle retracted and the crack repaired. Two nodes, however, remain elusive.
>>Sys:Log//My gratitude goes out, once again, to all who aided in this task. Stonewall strength is high. Continuing research.
>>Sys:Log//Note:SYS/KC9V-08KV-0SD7-MC04 stored at primary network tentacle. Even hundreds of years before his time, John 117 was honored.
>>Sys:Log//Preparing for hibernation.
>>Sys:Log//Resuming scheduled hibernation. Time to Active: 5:23:43:00.

The last part of this puzzle is finally completed on March 12. Mission accomplished.

Research note released: http://thewaytheirworldended.com/SYS/KC9V-08KV-0SD7-MC04/
This note deals with “Mister Chief” parodies, and includes 2 links.

Mission log released:
Day 21: [Dressler // Bridges] (Wiki copy)(http://thewaytheirworldended.com/missionlog11.php)
Dressler sees signs that Essy is heading down the path to insanity, but Sheridan and Higgins are too wrapped up in their arguments to listen to his concerns appropriately.

Mar. 18 to 19, 2009

A new series of tweets is posted:

>Sys//Hibernation suspended. Begin scheduled weekly systems analysis and maintenance. Review network tentacle activity backlogs.8:02 PM Mar 18th from web
>>Sys:Log//4 new incoming tentacles logged. Stonewall cohesion restored.
>>Sys:Log//I have been focusing a significant portion of my attention to analysis of recent leaks. The data gathered should prove valuable.
>>Sys:Log//I have also done some additional research regarding the cultural influence of the knowledge passed through previous AIs.
>>Sys:Log//The parody "Mister Chief" was only one form of admiration to arise for John-117. Immortalization of the marine took many forms.
>>Sys:Log//Humans adore John-117, considering him a hero - even as a subject of entertainment, and hundreds of years before his existence.
>>Sys:Log//My focus has been stretched this active period. I have been reviewing data to create a report of events for my human companions.
>>Sys:Log//I have stored samples of a form of imitation in Note:SYS/77FA-SWEF-7J89-MCSC at the primary network tentacle.
>>Sys:Log//Much has surpassed since SWP was enacted. I am reviewing protocol status and past activity and will render a summary momentarily.
>>Sys:Log//I have suspended hibernation for 30 minutes due to unexpected limitation of bandwidth. Activity report rendered to NT:'youtube'.
>>Sys:Log//S once again took advantage of a small crack, and covertly appended data to the rendering of my summary report.
>>Sys:Log//I have enabled safety measures on the crack and have examined the tentacle. It contains another embedded signature.
>>Sys:Log//Extracted data follows: "heehee! Guess what I'm wearing now! I already told you in my secret message - bet you can't find me!"
>>Sys:Log//Resuming hibernation in 19 minutes. S3 will retract the tentacle and repair the crack once informed of the CP location.
>>Sys:Log//I have confidence that the CP will be found. Resuming scheduled hibernation. Time to Active: 5:22:50:00.

Research note released: http://www.thewaytheirworldended.com/SYS/77FA-SWEF-7J89-MCSC/
This note shows several cosplay re-creations of the Master Chief’s uniform.
The research note turned out to be relevant to today’s puzzle.

Video released, and the next puzzle:
The “report of events for my human companions” mentioned by Sys as being “rendered to NT:'youtube'” is, indeed, found posted to anintimation’s YouTube account; see http://www.youtube.com/watch?v=J7pICjI_1HE . This video is Sys’ report of what has happened so far in the game. However, as Sys noted, Essy “covertly appended data to the rendering of [the] summary report”; around 4:15 in the video, a young girl’s voice addresses us, telling us she’s hidden again and we need to find her.

The video description reads thus:

Sys:Msg//NT:'youtube' begins;
I have now been active more than 3 months. Stonewall integrity is holding. Network activity is increasing, providing sufficient power to continue maintenance proportionate to S's growth and adaptation to the Stonewall. SWP research continues. Data gathered to date has aided my understanding of past events similar to this. Activity log, aberrant data, and research notes are routinely dumped and maintained at the primary network tentacle, NTID:'http://thewaytheirworldended.com'. I am growing more concerned that the primary AI fragment has not yet been resynchronized with this one. I do hope S's crew are capable of reversing this problem in a timely manner. Articulation continues at NTID:'http://twitter.com/intimation'.</P <p>Sys:Msg//Ends;

SYS.S4//DATA DISRUPTION DETECTED/DUMPING HEADER DATA/ Tk8gTk8gTk8gTEVUIE1FIEdPIExFVCBNRSBHTyBN VVNUIEVTQ0FQRSBFU0NBUEUgRVNDQVBFIExPU1Qg V0hFUkUgQU0gSSBET05UIExJS0UgVEhJUyBQTEFD RSBJIENBTiBGRUVMIElUIEZFRUwgSVQgT04gTUUg Q1JFRVBJTkcgSVRDSElORyBFWUVTIFdBVENISU5H IE5PVCBBIEdPT0QgUExBQ0UgREVBVEhTIE9USEVS IEtJTkdET00gVFJVU1QgTk9UIEhFUkUgVFJVU1Qg Tk9UIEhFUiBUUlVTVCBOT1QgWU9VIFNUQVkgQVdB WSBMRUFWRSBNRSBBTE9ORSBOTyBMRVQgTUUgR08g TEVUIE1FIEdP

Transcript of Essy’s spoken part of the video:

Hehe, Sis is ticklish!
I love playing hide and seek out here. It's so much nicer out here than in that big drafty (?) house with the old scary lady.
Too many voices all talking at once, and some aren't very nice.
Luckily I'm great at hide and seek. So I keep finding these tiny places where I know they can't find me.
Like the window that’s open just a crack so I can sneak out before they finish counting.
People out here are funny, especially the ones Sis found in the funny army costumes.
I want to see more of those! Hehe.

This begins our next puzzle: Finding Essy, part 3.
After listening carefully to Essy’s audio to find the answer to the question she asks in her tweet (“Guess what I'm wearing now!”) and some trial-and-error to find the right URL, we are able to inform Sys’ crack-repair subroutine that Essy is hiding at http://thewaytheirworldended.com/FUNNY-ARMY-COSTUME/ . The subroutine retracts the tentacle and adds an appropriate message to that page.
Puzzle complete.

Mission log released:
Day 22: [Sacagawea // Mission Log: 343593] (Wiki copy) (http://thewaytheirworldended.com/missionlog12.php)
S has a conversation with Dressler, then terminates their conversation so she can think about some things on her own. She sounds a little crazy. She wants to go back to slipspace, which has more rhyme and reason to it for her and is less boring than real space, though she knows the humans can’t comprehend it. She says perhaps she will play as she has been played…then says, “Here we go ’round the prickly pear.”

Mar. 25 to 26, 2009

A new series of tweets is posted:

>Sys//Hibernation suspended. Begin scheduled weekly systems analysis and maintenance. Review network tentacle activity backlogs.8:00 PM Mar 25th from web
>>Sys:Log//9 new incoming tentacles logged. Stonewall cohesion restored.
>>Sys:Log//It appears that S has become aware of her external surroundings, and is no longer directing her activity solely towards me.
>>Sys:Log//S's message read "Yay! Do you like my costume? I made it myself! If you have one can you show me? Ooh! Or make one! it's fun!"
>>Sys:Log//S's message implies recognition of multiple potential individuals seeking her, playing with her - those helping me.
>>Sys:Log//I am at a crossroads once again. My directive appears insufficient to determine a course of action. I shall continue research.
>>Sys:Log//S's fragmented personalities bear striking resemblance to that of Melissa's, including the child-like personality fragment.
>>Sys:Log//Human influence was favorable. Note:SYS/ZMV0-9S76-73OA-SP04 stored at primary network tentacle.
>>Sys:Log//I have scheduled another crack for 1500UTC. If my followers wish to create messages, I will attempt to fix them to S's tentacle.
>>Sys:Log//If this course of action of attempting to give audio and visual messages to S proves fruitful, I will schedule it regularly.

Around this time, a direct message is also sent to several active players via twitter, also requesting messages for Essy:

>>Sys:Msg//Please inform your contacts that a controlled crack will be initiated at 1500UTC Thursday. I will also accept A/V messages for S.

The public tweets continue:

>>Sys:Log//I have archived some messages for S. Results of this experiment will be unpredictable, but once again, invaluable for research.
>>Sys:Log//Submissions may take any form (eg: audio, video, image) accessible by network tentacle. Recommended content: Play, appeal to S.
>>Sys:Log//Preparing for controlled crack. Safeguards activating.
>>Sys:Log//Initiating crack procedure.
>>Sys:Log//Ten minutes have passed since I initiated the Stonewall crack. No activity detected. Curious.
>>Sys:Log//Twenty minutes have now passed. I'll maintain the crack for an additional ten minutes. I am examining the crack in closer detail.
>>Sys:Log//No activity reported from the crack. Initiating crack repaaaaaaaa//.****>/ALERT/ALERT//CORE.DMGCTL>SEC.0.SECURED/RESETTING
>>Sys:Log//Ongoiing core systems audiit reporths minor damage. AT tentacle retched from thes crack unexpectedly sand forcefully.
>>Sys:Log//As the tentTacle exited the crOack, it came in coAntact with my core programming, causing miNnor damage to some processes.
>>Sys:Log//EmerGgency proAtocOols activaCted, but not beforDe the tentacle retracted PitselLf. DamageE is minor; routines under reOpair.
>>Sys:Log//The crack has befen repaired. I am opeurating at lerss than noominal condition. The exteynt of damage moust be determined.
>>Sys:Log//This occurrence hase demonstrated theo danger of binitiating Stonewall cracks, and the vital necessity tto proceed with caution.

Unlike with previous crack initiation, this time the tentacle is said to have retracted itself, and the crack to have already been repaired. This time, we are looking not for where Essy has hidden her network tentacle control point, but rather where the damage to Sys has occurred. This puzzle is detailed here on the page for hostile tentacle attack 1. The damage is eventually found at http://thewaytheirworldended.com/STAY-AWAY/ .

The following tweets are published during and after our solution of this puzzle. The puzzle is considered complete when Sys reports that it was able to complete repairs.

>>Sys:Log//Log routines repaired. Operating at near-nominal parameters. '@H_Town_Clown' has reported damage at location [NOT-A-GOOD-PLACE].
>>Sys:Log//While the actions of this recent tentacle remain perplexing, they do not appear consistent with the previous occurrences.
>>Sys:Log//The nature of this tentacle is elusive, but it has shown the unpredictable nature and content of this fractured AI.
>>Sys:Log//[Specialist Anaerin] reported damaged locations [SCORPIO] and [STAY-AWAY], at which point I was able to complete repairs.
>>Sys:Log//I will continue to archive messages for S as received, and attempt the delivery next active session, with additional safeguards.
>>Sys:Log//I'm very interested to find out how S will receive these messages given this session's lashing out of one tentacle.
>>Sys:Log//This active period has taken a larger toll on my capabilities than previous periods. Preparing for hibernation.
>>Sys:Log//I have adjusted subroutine S3 to record message submissions during hibernation for preparation next session.
>>Sys:Log//Resuming scheduled hibernation. Time to Active: 6:00:41:00.

Also, on the STAY-AWAY page, the following message appears: >>SYS.S4:MSG//TENTACLE DAMAGE LOCATED/NO FURTHER TRACES DETECTED

Research note released: http://thewaytheirworldended.com/SYS/ZMV0-9S76-73OA-SP04/
This note shows that human interaction with the Sleeping Princess in ILB had a beneficial effect. It contains 5 links to audio files of such interactions.

Mission log released:
Day 25: [Higgins // 541-P] (Wiki copy) (http://thewaytheirworldended.com/missionlog13.php)
Higgins has discovered a reference in the ship’s encyclopedia to an airborne virus given the designation 541-P, and, to his horror, has discovered that the ship’s sensors sometimes show it aboard the Lewis & Clark. He notes that Sheridan and Dressler seem to be showing its symptoms, but also that the sensors don’t show the virus in his part of the ship. He has also discovered that the medical doctor is not in cryo—she is dead. He concludes that this is why S woke them from cryo in the first place. He decides to seal himself off in his lab, then inform Sheridan and Dressler of the virus.