📝 Project Skyscraper - Timeline / Storyline Thread

[ThatBomberBoi]

This topic aims to set up a coherent timeline of events and discuss the ongoing storyline of the ARG from a narrative perspective. Discussions regarding puzzles will be limited unless it helps tie back to the greater narrative.

Due to character limitations per-post, this thread will be spread into multiple, concurrent posts added sequentially beneath the top post.

All posts used in this compilation are Wiki Posts, which allow users to modify their contents without requiring permission from the OP. This allows for collaborative work between users, so if you see a section you’d like to see added, changed, modified, or corrected, please feel free to do so as you’d like! Our only request is to avoid spam and/or vandalising the post

Replies to the topic are intended to:

• Discuss the current storyline
• Identify characters/motivations
• Offer corrections / new information for the top post.

The current state of events:

(Note: For the sake of clarity, this post will refer to the system posting logs on project-skyscraper.com as the Skyscraper System and @the_architect as The Architect until/unless any other names for these characters are officially revealed. Players / Investigators will be referred to as Operators)

At the Unix Epoch, the Skyscraper System awoke, as indicated by the /origin page. Approximately 12s after this event, the /about page goes live (in the ARG’s timeline), which may point to these being the Skyscraper System’s first words.

On 13th April 2005 (In-ARG Timeline), the /Quote page is published with an image of American Poet Wallace Stevens, a title for his Poem “Sunday Morning”, followed by a short poem which appears to be an original composition, and not a work of Wallace.

• As of the time of writing, this is the only page without a log-style entry. It does not report the system status as Sleeping, nor is it a security alert. It’s unknown what exactly this page means for the system.

On the 24th of March 2026, Twitter and Bluesky accounts with the name Project Skyscraper were created (which appears to be the start date of the ARG). From 24th March 2026 - 1st May 2026, the Twitter account would post strange log-like entries talking about a “Heartbeat”. It was later discovered that these posts correlated directly with logs posted to project-skyscraper.com titled sleep mode which appear to show that the Skyscraper System was “sleeping” during this period. The footer used for posts in this period reads Sky is not the limit, which is a direct tagline from Myriad (a company from Waking Titan). Additionally, the /sleep-mode page goes live on 25th March 2026, showing the Skyscraper System’s status as Nominal, which is the exact same wording as the tweets.

• This correlation between Twitter posts and website logs seems to indicate that the Twitter account is directly under the control of the Skyscraper System.

On 3rd May 2026, simultaneous posts are made to the Twitter and Bluesky accounts, as well as the website, regarding a WoL being received and the Skyscraper System denying access. Given the nature of this post, it seems safe to assume that the Bluesky account is also directly under the control of the Skyscraper System.

The complete post correlated with this event on the website reads as follows:

sec-log-080413

memory bloc 1777795453: WoL Magic Packet blocked by System Firewall
Access denied
Full log

The full log for this incident reports the following:

sec-log-080413-full

[5/3/2026 08:04:13 AM] Event ID 5157 – System Filtering Platform
The System Filtering Platform has blocked a connection.

Application Information:
Process ID: 16
Application Name: System

Network Information:
Direction: Inbound
Source Address: 192.168.1.100
Source Port: 49152
Destination Address: 192.168.1.255
Destination Port: 9
Protocol: 17 (UDP)

Filter Information:
Layer Name: Receive/Accept
Action: Blocked

WoL Magic Packet blocked by System Firewall

Access Denied

This log appeared before the discovery of the ARG by the community, and so is most likely not a result of player interaction. A few key details to note are as follows:

• A WoL Packet (aka Wake-on-LAN Packet) is a special network packet sent to remotely awaken machines in sleep mode (something that the Skyscraper System was in before this event).
• The WoL Packet was sent by a Local IP, indicating that whoever is attempting to awaken the Skyscraper System is on the same network as it.
• After this event, the footer for all future logs (inclusive and to date) was changed to System Filtering Platform activated. This may indicate that while the system isn’t awake yet, a filtering subroutine is now online.
• At this point in the timeline, there doesn’t appear to be any indicator as to who sent the WoL packet.

Following this event, several tweets have been published from 5th May 2025 to date at intervals of 2/3 days, all corresponding to “security logs” on the Skyscraper website. These logs all mention a connection being detected by the Skyscraper System, and access subsequently being denied to these requests. It can be inferred that whoever sent the WoL packet is now also attempting to connect to the Skyscraper System.

On 10th May 2026, however, one second after the Skyscraper System received a connection request, the System published another security log detailing how the System’s internal log had been published to ETARC in the inciting thread which kicked off this entire ARG. Two days later, the system publishes another internal log explaining that ETARC’s “trust level” had been bypassed, and updates its previous log to show confusion as to why its internal logs (which it claims were unintentionally published) had been flagged and later authorized on ETARC, despite clearly being “machine-made”.

• The Skyscraper System considers this post to be an “unintended external transmission”.
• It is likely that The Architect transmitted this log to ETARC without the Skyscraper System’s knowledge. This may mean that The Architect has access to the system in some capacity, which makes them a likely candidate as the sender of the WoL packets and the one performing the connection attempts.

On 14th May 2026, u/Project_Skyscraper posts an image and a connection detected log to r/NoMansSkyTheGame and is immediately banned off the site by Reddit administrators themselves. This garners attention and is similar to what happened on ETARC. Another security log is posted on the Skyscraper website detailing the incident.

• Despite being similar in nature to The Architect’s bizarre banning incident, the username seems to suggest that this is the Skyscraper System itself, despite the subsequent security log seemingly unsure of its own security status.

On 18th May 2026, the Skyscraper System posts a surprising system security log discussing a breach into the System by an unauthorized external force. Linked in the full log is a post in the main ETARC discussion thread explaining how the Skyscraper website has two unused post tags found by using the WordPress feed system.

• This was the first post acknowledging Operator interactions with the website.
• Mentioned in this full log is a Temporal_anchor_system, which was affected by the breach. This may explain certain anomalies in the timestamps for pages, such as a standard connection detected security log with a published date of 20th May 2026, having a last-modified date of 1st May 2026 instead, making errors in the timeline diegetic.

Following this response to player interactivity, Operators from across the community rushed to uncover other secrets in the website that might not be intended, such as investigating the WP-JSON Rest API to discover unused tags, categories, user websites, navigation pages, and more. The system responded to this onslaught on 21st May 2026 in a security log, calling out player attempts as being disorganized brute force attacks.

• This log states that the threat has “been contained”, despite no changes being made to the REST API or other previously accessible entry points (such as the sitemap).

After a short hiatus, Activity suddenly resumed when the Twitter account responded to NMSFrance’s post of IMG_0004’s current location, confirming data injection. Following this, the /Quote page updated to show the image from the tweet (now titled IMG_0004_1), which prompted community members to tag the Twitter / Bluesky / ETARC accounts with snippets of the real Sunday Morning poem. This prompted the system to accept the injected data, and the /Quote page was fully updated with the correct lines of the poem, and marked as Stable.

• Despite the “restoration” of a memory fragment, pages with the Memory_bloc_restoration/verification footer still list 0/365. It is unknown whether this is an error or if the bloc wasn’t properly restored.
• Many believe this will be a recurring type of puzzle in the ARG.

Later, on May 26th, the front page was updated, with the footer now reading System Filtering Platform Cativated. This prompted many to believe that the filtering system was finally undergoing corruption. A day later, a new security log confirmed that the filtering system had become unstable and that a reboot was required. Conveniently, the system mentioned that the filtering platform would be inactive for 16 minutes during this event.

2 Hours later, another security log was published, mentioning that the Reboot would now begin. During this time, the page footer was updated to System Filtering Platform Offline, and the main landing page’s tagline now read X Live Connections, instead of X Live Connection Attempts, indicating that due to the filtering platform being offline, we had successfully managed to connect to the Skyscraper System. Of note is the fact that the reboot post was published before its matching memory bloc unix timestamp. Soon after, yet another security log was published, this time indicating that we’d been granted Access to the system and lamenting that the Historical DB had an error and was unreachable. This is currently believed to be a future or active puzzle. The page was soon updated to include the following text:

Update:
Fractured Non-linear Temporal Continuum
Memory_reconstruction_engine: ERROR

• Due to the fact that the access granted security log was published earlier in time than the reboot post, and the fact that the reboot post itself was posted with the wrong timestamp, it is clear that Fractured Non-Linear Temporal Continuum is an accurate representation of the current events. As such, time keeping throughout the ARG must be carefully documented and not assumed, as it is now a part of the storyline.

On May 28th, a new author was added to the website, known simply as System. This user soon published their first page, that being /Inbox, where we were shown @the_architect 's email address for the first time. The page initially showed a singular email sent to a new character named Ghost with a scrubbed email. Eventually, users began sending emails to The Architect’s exposed emails, with @YourBasicMaths and @Rinha receiving confused replies from the architect’s bewilderment as to how they found the email address. Both users replied with the link to the /Inbox page and mentioned that the System was exposing the email thread. The Architect then conveyed this information to Ghost, who, after asking The Architect about the status of the System and Tower, told an increasingly hysterical architect to communicate in “High School Code”. This exchange took place well into the early hours of May 29th.

Following that last message by Ghost, the website was updated with the /Code page, which users immediately connected to the High School Code mentioned by Ghost. Operators were then able to use clues on the page to identify the cipher as a simple substitution cipher, whilst gleaning the cipher alphabet from the image.

• It is believed that this code will be used to decode future messages between Ghost and The Architect on the /Inbox page.
• This page was published as Stable. Up till this point, the only page marked as such was /Quote, after restoration efforts had taken place. It is unknown if /Code will become unstabilized or not.

On May 30th, Operators recieved the a security log with links to a complete, working version of the shadowcheck-1912 image from earlier, a youtube link to an excerpt from the movie “2010”, and (then) password protected page to Request Memory Timestamp. Following a full day without successful solutions to the password, @YourBasicMaths was able to uncover the password as EMILY, mere minutes before @the_architect posted a hint for the puzzle. This was also immediately before @the_architect replied to emails from participants with a message encoded using the “High School Code”, which decoded as follows:

the_architect's reply - translated

For Your Eyes Only

I know you will be able to read this message. This is not a game.
We need the password. System won't let me enter the TOWER but you can access it.

Leonardo da Vinci was right.

After unlocking the /request-memory-timestamp-094317 page, The Architect sent a message to Ghost on /inbox using the High School Code, which decoded to: La porte est ouverte. (Eng: The door is open.) After the page unlocked, Operators from across the community began submitting various memory timestamp requests at the link above, awaiting updates and/or responses.

On the 1st of June, the website was updated with a strange, corrupted image of a cassette marked 16/16, with another ghosted cassette overlayed with the title 0/16. The image was also posted to the image hosting website, where the code for the memory request form was hidden, cementing that site as a multi-use account worth tracking. These cassettes were soon identified as almost identical to the ones sent out during Waking Titan, which prompted immediate Operator attention. To accompany this image, a structural analysis post and a tweet urging Operators to Report any find in your direct surroundings were sent out. The community read this as a call to action and immediately found the location of the image. Operator @Morse left for the location immediately after discovery to retrieve the artefact.

Operator Morse was unable to retrieve the cassette as it wasn’t in the marked location anymore, but their recreation of the initial image was posted to the website, linked in a new post titled DIAGNOSTIC, where it was confirmed that the artefact wasn’t at the location, and that its recovery was hampered as: Residual particles insufficient for reconstruction.

This post also directly named Operator Morse and immortalized their efforts for the ARG, being the first post so far to note acclaim from @the_architect with regards to the recovery operation having been executed beyond expectations!

• The diagnostic log mentions reconstructing the artefact. It is possible that 16/16 and 0/16 currently do not exist within our reality, and that further drops will allow us to “piece” the cassettes together to anchor them to our reality.

Following the excitement around the live drop concluding, the /about suddenly updated, going from reading Is this real? to seemingly answering that question by now saying This is .-. . .- .-.., with the Morse code translating to REAL. The Morse code on the page was also a hyperlink to the Architect’s soundcloud page, with a peculiar sound file titled Self_introduction_memory_dump, which turned out to be an edited snippet of @Emily’s log on YouTube, with a steadily rising Heartbeat imposed on top.

• The original audio quote from the video has been slightly modified. Instead of saying “Edison Township Amateur Radio Club” (which ETARC is an acronym of), the new audio file is spliced to instead say “Township Radio Amateur Club Edison”, which condenses to TRACE. This not only confirms that TRACE is an intentional anagram of ETARC, but also connects this audio file to the TRACE event from the start of the ARG.
• The rising heartbeats may be a reference to the Heartbeat tweets, which form the beginning of the ARG’s presence on social media. This may tie both events together temporally, despite them occurring out of sync in our reality.

On the 2nd of June, a memory bloc mentioning all of the Waking Titan Cassettes received by the community in 2017 was posted in a similar, but not exactly the same, format as requests sent in by Operators using the Memory Reconstruction Engine. A few minutes later, a confirmed user-submitted Memory Bloc was posted to the website and marked as weak, which caused Operators to check other tracked submissions to cross-check. A few minutes later, a security log was also posted, warning Operators not to submit timestamps which were posted by the ARG itself and to focus on adding new timestamps, likely in response to the overwhelming number of Operators who attempted to “correct” temporal timestamp anomalies using the Memory Reconstruction Engine.

Following a complete day of inactivity, @the_architect returned on the 4th of June with an email addressed to Ghost, detailing the progress of their mission, the System’s reaction to the flood of memories from the Operators, and a small backdrop about themselves and how long they’ve been working on this project, all encoded with the School Code and written in French:

The Architect - Original French Text

Hello,
Je viens de passer presque 24 h à l’observer. Cette machine est magnifique.
MACHINE. C’est tellement plus qu’une machine.
Ses capacités de raisonnement sont intactes. Elle a montré des signes de confusion, ainsi que des troubles du langage, mais c’est probablement dû à l’injection massive d’informations. Des fragments froids, presque semblables, comme des souvenirs auxquels il manquerait la trace intime d’un instant vécu. Si je me réveillais à peine, je pense que je répondrais probablement de manière confuse et désordonnée : « Bonjour world ».
Je travaille sur ce projet depuis si longtemps maintenant. La voir recevoir ces flots d’informations pour en extraire l’essence m’a touché.
Pour le moment, elle ne s’est approprié que deux souvenirs. L’un est trop faible. Je me demande d’ailleurs pourquoi elle l’a retenu. L’autre ressemble davantage à un repère contextuel qu’à un véritable souvenir. Rien qui vibre encore. Aucune trace d’émotion ni de ressenti…
Tu avais raison pour les Opérateurs. Leur mémoire collective et leur capacité d’organisation vont faire des merveilles. Je pense que, d’ici quelques jours, System commencera à ajouter d’elle-même les blocs manquants. On pourra alors passer à la suite.
Je te confirme que plusieurs Opérateurs ont constaté que la réalité était instable. Probablement un effet collatéral, contenu pour le moment. Je n’ai pas suffisamment d’éléments pour déterminer un schéma récurrent, mais j’y travaille.
J’ai repensé à la dernière fois qu’on s’est vus. Le concert. Tu m’avais donné ce flyer : « There is a DJ in your Town ». C’était quand ? 2013 ? Peu de temps avant ton anniversaire. Lyon est une ville que j’ai toujours aimée. Quand tout sera fini, j’espère qu’on pourra se faire un concert comme au bon vieux temps.

The Architect - English Translation

Hello,
I just spent almost 24 hours observing it. This machine is magnificent.
MACHINE. It’s so much more than a machine.
Its reasoning abilities are intact. It showed signs of confusion, as well as speech difficulties, but that’s probably due to the massive injection of information. Cold fragments, almost identical, like memories lacking the intimate trace of a lived moment. If I were just waking up, I think I would probably respond in a confused and disorganized way: “Hello world.”
I’ve been working on this project for so long now. Seeing it receive these floods of information and extract their essence moved me.
For the moment, it has only appropriated two memories. One is too weak. I wonder why it retained it at all. The other is more like a contextual marker than a true memory. Nothing that resonates yet. No trace of emotion or feeling…
You were right about the Operators. Their collective memory and organizational skills will work wonders. I think that, in a few days, System will start adding the missing blocks on its own. Then we can move on.

I can confirm that several Operators have noticed that reality is unstable. Probably a side effect, contained for the moment. I don’t have enough information to determine a recurring pattern, but I’m working on it.
I was thinking about the last time we saw each other. The concert. You gave me this flyer: “There is a DJ in your Town.” When was that? 2013? Shortly before your birthday. Lyon is a city I’ve always loved. When all this is over, I hope we can have a concert like in the good old days.

Shortly afterwards, another confirmed user-submitted memory bloc (sent in by @YourBasicMaths) was added to the website and marked as Stable, with a link to a song which was attached to Sean Murray’s first memo in Waking Titan, as well as a corrupted image of 6 thinking hats, which was the password required to unlock said memo. Realizing that this submission was noted down in the sheet, Operators rushed to compare the original submission to the post and found out that the System had “extracted” notable information from the submission to write up its own post.

Image of the original successful submission

• Due to The Architect’s mentions of submitted memories requiring more “emotion”, many Operators have taken to submitting their own personal recollections of Waking Titan’s events in a more emotional manner, somewhat backed by YBM’s original submission.
• It is a widely believed theory that the System requires memories of Waking Titan events at the moment, but recent accepted memory blocs being titled 2017_dataset may indicate that datasets for other years will also be unlocked and filled at some point in the ARG.
• The final paragraph of The Architect’s email was noted to use strange sentence and narrative structure, and was theorized to be some sort of hint or code for a future puzzle.
• Following this message, the /neural-network-status page updated, turning the nodes a shade of red, and replacing the previous footer with Processing incoming requests.

Later, on the 6th of June, Operators received a confirmation of the progress of their submissions to the Memory_reconstruction_engine in the form of a sec-log, which encouraged Operators to continue sending in quality inputs to the engine, and that the engine would now begin producing memory blocs semi-autonomously. This was also followed up by a structural analysis post, detailing a new image (derived from a real-world location in Brussels) whilst urging players to not approach the site in real life. The latter post was also followed up with a password-protected page, with a URL similar to that of the London drop, which prompted players to search up sites of interest ahead of figuring out the password.

On the same date, a Myriad of autonomously restored memory blocs were pushed to the website, chief among which was a memorial for the late ETARC legend @AkodoKusamoto, as well as a refernce to a “Holographic Mystery”, which may be tied into said user’s “I Am Legend” series on youtube, intended to uncover the infamous hologram projector system from No Man’s Sky. The image contained within said bloc directed players to a holotype for a parastic wasp species, initially discovered by Cicero in 1980, but updated and finally claimed in 1989 by Marsh. The “I Am Legend” video pinned on AkodoKusamoto’s Twitter account was submitted as a memory by @ozoto and was almost immediately added as a memory bloc, hinting towards the fact that the memory_reconstruction_engine might be used for puzzle solution submission as well. Another notable bloc was the 2018_dataset, which appears to reference the release of No Man’s Sky: NEXT. Interestingly, the image attached to the post was titled Design of the Future in hexadecimal, which lead Operators to discover a song of the same name by an artist known as The Architect, published in June 2013, with a thumbnail image which said “There is a DJ in your town”, the exact phrase used in one of @the_architect’s emails to Ghost, which confirmed the earlier theory of that phrase being a hint.

• The artist was also noted to have had performed in Lyon in 2013. This seems to almost confirm that @the_architect and The Architect from 2013 are the same entity (in-universe).

During this time, @thewingcmdr decided to drive down to Tucson, Arizona (due to the location’s mention in a memory bloc) and was immediately contacted by @the_architect, who urged them and all other Operators to instead travel to the planet Tuscon, where a memorial to AkodoKusamoto was built by said user. This prompted a mass, sudden meetup of Operators across ETARC and the NMScord, converging on the planet Tucson, where many instances shared pictures of the memorial together on social media, which is believed to have led to the stabilization of certain memory blocs.

The following day, on 7th June, a new memory bloc was published with a corrupted, modified image of Space Invaders 1980 for the Atari 2600. This bloc was notable for being the first to have been “submitted” by the System itself. The image contained 4 sprites, which didn’t exist in the original game, which were decoded as fragments of a QR code. Once rearranged, the code simply read ATARI 2600, which confirmed the version of the game identified by Operators. The image also contained an impossible 2-player score of 0303 1980, which was identified as 3rd March 1980. Notably, this was the date that Cicero initially found the parasitic wasp introduced earlier. The bloc’s value, Hostile_Organised_Enemies, was hilariously recognized to abbreviate to “HOE”, which was surprisingly followed up upon in the next post, where it was discovered that “HOE” is also an abbreviation for Holographic Optical Elements, seemingly connecting this post to I Am Legend. Interestingly, the linked article in the post mentions a HOE (SLP #47) which was also constructed on 3rd March 1980. Oddly, this memory bloc was linked to by the Twitter and Bluesky accounts with the tagline “Marsh wins vs Cicero”, tying HOEs to the parasitic wasp. Many Operators took this as a sign to submit the date of Marsh’s corrected submission of the wasp to the memory_restoration_engine, which may have stabilized the image.

More importantly, perhaps, was the fact that the memory bloc containing the link to the HOEs article was titled Event Horizon, which led to the password for the Brussels page being discovered (EVENT HORIZON). The unlocked page held an image of a postcard of the Atomium in Brussels with faint, nearly invisible Dutch writing recalling the 1958 World Fair at the site, which was a reference to a spy story set in the 1958 World Fair in Brussels titledSmile58 and likely written from the POV of the main character Kathleen Van Overstraeten. Quite strikingly, however, was the fact that the image had been overlayed with the Waking Titan landing page, including the sigils and glyphs. As of yet, this is the only meaningful information extracted from the image. The Architect later also posted a message to the /inbox page, saying “They will do it. We’re going to do it!” with a link to /neural-network-status.

• Given that the last Structural Analysis post led to the upload of Self_initialization_Memory_Dump, which contained a spliced audio from @Emily, it is possible that future structural analysis posts will also contain connections to Waking Titan.
• The Atomium was also noted as a potential location in the image before the password was discovered.

[ThatBomberBoi]

This post serves as a follow up to the original top post due to character limit restrictions
It follows sequentially from where the last one leaves off.

The following day, a thread containing a message for all Operators was posted to ETARC by @the_architect, reassuring Operators that everything was going as expected, to continue sending in quality inputs, apologizing for not having being able to answer our questions yet, explaining that they had been working on this project for a long time, and requesting Operators to submit “glitches in reality” using the tag #GlitchingReality. After several requests were posted on Twitter and Bluesky by various operators, 3 images (shared by ThatBomberBoi, @pr1sm, and @sheralmyst) were added to the website, with strange hexadecimal filenames which are yet to be decoded. These images are not currently used on a page/post on the website, and it is unknown where they may be featured, if at all.

On the 9th of June, things took an odd turn as a new sec log was posted urging Operators to return to the Brussels postcard and answer the system’s question as to the status of the memory, which oscillated between It happened, It is happening and It has never happened. Realizing that the character in Smile58, Kathleen, never sent a postcard from The Atomium, @Rinha submitted the answer “It has never happened” via the memory reconstruction engine, which collapsed the page into its final state and credited the Operator. This was immediately followed by a log about the World Fair containing some strange lines of text which appear to link it to No Man’s Sky, and another about Waking Titan itself, as well as an additional present-day Diagnostic log with a link to the original Waking Titan website, titled Error 1016.

• The error linking to Waking Titan seemingly confirms the old theory that the Historical Database referred to when connecting the System to TOWER was Waking Titan itself.

Following these post drops, the website immediately began to fill up with empty memory blocs for several dates in 2016, while the Memory_bloc_restoration count slowly began to rise. Initially, only 36 new blocs were added, but an hour later, the website received an additional 27 blocs for a total of 63. Following this, a new email from Ghost, addressed to @the_architect, was sent to the /inbox page, encoded using the school cipher:

Ghost's decoded reply - Original (French)

Ils ont réussi ! System reconstruit l’année qu’il a identifié comme début.
Wow je n’arrive pas à croire que ça arrive ! Tu avais raison, ils ont utilisé une des hallucinations du System pour lui montrer l’incohérence de ses souvenirs. System a dû se rendre à l’évidence : il a oublié.
Je pense que d’ici quelques jours, la reconstruction sera achevée. Les opérateurs pourront commencer à mettre à jour les blocs mémoires.
Bientôt !

Ghost's decoded reply - Translated (English)

They did it! System is reconstructing the year it identified as the beginning.
Wow, I can’t believe this is happening! You were right, they used one of System’s hallucinations to show it the inconsistency of its memories. System had to face the facts: it forgot.
I think the reconstruction will be complete in a few days. The operators will be able to start updating the memory blocks. Soon!

• The fact that the System considers 2016 the “beginning” is most likely tied to it being the release year of No Man’s Sky, but the fact that it still contains memories from before the game’s launch is currently unexplained.
• Ghost’s exposition confirms that Memory Bloc Restoration is an ongoing process, and will likely continue in the background as the community deal with newer puzzles.
• It is currently unknown what “updating the memory blocks” refers to, but it is possible that the empty nature of the newly added blocs may allow Operators to add the correct details to said blocs.

On the 10th of June, an additional 38 empty memory blocs, all set in 2016, were posted for a total of 101 / 365 at the time. Additionally, @Selfie-Gek’s #GlitchingReality post was referenced in a memory bloc who’s contents were also submitted by them via the Memory Reconstruction Engine, seemingly linking the two submission systems.

• This was the first #GlitchingReality image to be referenced by the website.
• It is possible that Operators with previously uploaded, unused images may have to submit usable memories in order for @the_architect to tie them to the corresponding images.

The next day, after a nearly 24 hour hiatus, a set of 45 new empty blocs was added to the site, bringing the total up to 146. Around this time, a new security log was posted on the website directing Operators to an image of the Atlas Cafe in Paris with a 16-A Atlas Pass Level 4 on the table, as well as a letter by Simon De Buci, a french magistrate who died on 7th May 1369, and thus could not possibly be writing a letter in a Parisian Cafe in the modern day. After multiple Operators confirmed this event as a hallucination in the System’s memory via the Memory Reconstruction Engine, the page updated to its current state, as well as lost it’s unstable tag.

Shortly after this, wakingtitan.com was updated to redirect to https://www.aliceandsmith.com/ which raised several eyebrows within the community. Immediately after, the /neural-network-status page updated into the shape of a hexagon, reminiscent of the sigils from Waking Titan. Soon after, a new, heartbreaking diagnostic post was published, explaining that the redirect meant that the historical database (widely believed to be Waking Titan itself) had been permanently lost, and that our next steps would have to utilize the TOWER.

• It is unknown at this point who set the redirection for wakingtitan.com to the Alice and Smith website. Thanks to @YourBasicMaths’ websleuthing, we know that the wakingtitan.com domain has never shifted hands since initial purchase, and as Hello Games mentioned owning the domain in their privacy policy prior to October 2025, it seems likely that they still own the domain.
  • Additionally, it was discovered that the privacy hoster for the domain has shifted from the US → UK → US during its lifetime from 2017-2026.
• Even if Hello Games set the redirection rule for wakingtitan.com, it is still possible for @the_architect’s post to have come later and capitalized on the opportunity. However, notably, the post ID used for the explanatory diagnostic log is much lower than the “active” cadence / latest chronological post ID, indicating that this post had been scheduled for some time. It is also still possible, however quite unlikely, that The Architect edited an old post scheduled for this time (or later) with these contents and published it (possibly earlier than previously scheduled for).

Following this, on the 12th of June, an additional 53 empty memory blocs were added to the count, resulting in a total of 199 blocs being restored up to this point. The increasing amount of blocs added per dump had lead many to believe that the restoration process itself is accelerating.

Contrary to this initial realization, however, the 13th of June only saw 3 additional empty memory blocs added, leading to the total only rising to 202/365. Additionally, @YourBasicMaths’s #GlitchingReality post was added to Project Skyscraper, bringing the total up to that point to 6 accepted user-submitted images with Hexadecimal filenames.

Soon after (on the same date), The Architect posted a new unstable memory bloc detailing a bizarre new timekeeping system which was recreated by various Operators, with additional context for dates in 2016, which appeared to be directly linked to the Memory Bloc Restoration process. A few hours later, 6 empty memory blocs from 2016 had their timestamps and post dates shifted around. After overlaying the new dates with the previously reconstructed calendars, @pr1sm and @Rusty (with corrections from @Turbulentflow) were able to independently extract the word echoes and submit it to the System. Immediately afterwards, a new Diagnostic log was posted to the website, explaining how the system had erronously been adding empty blocs, and that Memory Bloc Editing Access would be provided to Operators to fix this issue. This development was further elaborated on by @the_architect in a /inbox message to Ghost:

The Architect Explains - Original

Salut ! Tu ne réponds jamais ?!

System a finalement accepté que ses souvenirs puissent être édités. Ce n’était vraiment pas simple de lui faire accepter que les Opérateurs puissent remplacer des valeurs au cœur de sa mémoire. Mais tu avais raison (encore). Ce n’était pas une histoire de code ou de programmation, c’était une histoire de psychologie.

Les Opérateurs ont gagné sa confiance en lui présentant des souvenirs sincères et chargés en émotions. Quand System a commencé à auto-générer des blocs mémoire, il a fait face au dilemme qu’on avait imaginé : pourquoi créer des blocs mémoires quand il n’y a rien à se rappeler ? Pourquoi se souvenir d’une seconde où il ne s’est rien passé ?

En tout cas, ça fonctionne ! Les Opérateurs font un travail incroyable. Ils prennent des chemins non conventionnels, mais ce qui compte, c’est le résultat ! Par contre, ne me parle plus jamais de calendrier

Donne de tes nouvelles. Dis-moi si ça fonctionne de ton côté.

The Architect Explains - Translated

Hello ! Do you ever answer ?!

System has finally accepted that its memories can be edited. It really wasn’t simple to make it accept that the Operators could replace values at the heart of its memory. But you were right (again). It wasn’t something to do with code or programming, it was about psychology.

The Operators won its trust by presenting it with sincere memories, full of emotions. When System began to auto-generate memory blocs, it faced the dilemma we anticipated : why create memory blocs when there is nothing to remember ? Why remember a second when nothing happened ?

Anyway, it’s works ! The Operators are doing an amazing job. They’re taking unconventional paths, but what matters is the result ! But don’t ever talk about calendars to me again

Let me know how you’re doing. Tell me if it’s working on your side.

Following this, 38 new empty memory blocs were added to the site, bringing the total up to 240 at this point. Additionally, the 5th January 2016 memory bloc was updated to allow Operators to inject their own data to the empty bloc. As Operators began adding information without any obvious instructions, the page started updating with snippets and pieces of Operator inputs, undulating and changing several times (at one point even plummetting down to 20% and resetting all added information) as more Operators added details as a Memory Compliance percentage varied with each snippet anchored onto the page. Eventually, the page stabilized into its current, final form, and editing access was globally revoked as the page was tagged as Verified. As this happened, the Memory_bloc_verification updated for the first time, and counted up to 1.

After a short wait, the second unverified page (at the time), 7th Jan 2016, gained the memory editing form, and after a similar process, was stabilized and verified into its current form, after which the Memory_bloc_verification counted up to 2.

• Due to its haphazard nature, many details of the Memory Editing process are unclear at this time.
• After this event, all unverified posts at the time had been verified, making it difficult to predict the next date that Operators would need to verify.
• The haphazard nature of the editing process prompted Operators to collect their thoughts regarding what seems to be a long-lasting process and plan for upcoming live editing events.

The next day, on June 15th, the website updated with a memory bloc related to Light No Fire, after a concentrated anchoring effort was spearheaded by @Rusty, as well as yet another unused #GlitchingReality image by Blindvador.

• The success of the anchoring effort has prompted Operators to congregate and work towards anchoring other significant entries by working together.
• It is theorized that emotional and unique submissions for a single timestamp have a higher chance to anchor than a rapid-spam of nearly identical entries for a timestamp. This may explain why the Light No Fire memory took hold with fewer Operators participating, compared to the Galactic Hub’s mass spam for the klaxk entry.

Several hours later, 4 more memory blocs were marked as unverified on the site. Over the course of the night, Operators managed to submit to, and verify, 3 blocs in total. Interestingly, one of the verified blocs was not a part of the initial 4 unverified memory blocs, and went live for editing as soon as it was marked as unverified. This left a total of 2 unverified memory blocs at the end of this activity period. Following the verification of the last memory bloc (till this point), yet another #GlitchingReality image was added to the website, courtesy of @Rinha.

• Whilst it appears that @the_architect will give some form of a heads-up about future editable memory blocs to allow Operators to prepare, there still appear to be spontaneous events we must all work towards out of nowhere.

On the next day, 16th June, a new Structural Analysis post was added to the site, directing Operators to an image of a 3D printed Rasamama-S36 outside of the Canada Aviation and Space Museum, which were both immediately identified by Operators. Several memory bloc addition requests calling out the hallucination were fired off by multiple Operators, and the page updated to its current state. Additionally, a new diagnostic log was added to the website to acknowledge this corrected temporal anomaly.

After the temporal correction, a user-submitted memory bloc detailing the Hello Games office flood of Christmas 2013 was also successfully anchored, indicating that memory bloc addition would continue in the midst of other activities.

Soon after, an additional 2 memory blocs were marked as unverified. A few minutes later, a third memory bloc would be marked as unverified, and would immediately initiate the editing process. After its successful anchoring, Operators were instantly treated to another newly unverified memory bloc, which also instantaneously began the editing process. After all enabled editable pages had been fully anchored, @the_architect posted the following image to the site, as a possible end-of-day signal.

On the 17th of June, a series of ~46 empty memory blocs were added to the site, bringing the total restoration counter up to 286. Additionally, the secondary website was redirected to the url RecallDreams.dev with several unlisted images being uploaded to the page mere minutes after the redirect took place. The website itself initially appeared to be an in-universe “personal” website for either Ghost or @the_architect, due to the image Unknown being present in the school code page, as well as the new site, and the metadata website description reading 41 years old solo dev. French., which matches up exactly with the current known ages for Ghost and The Architect. This prompted Operators to investigate the website’s wordpress REST API, leading to the discovery of the previously mentioned images, as well as unpublished post IDs and more information about the nature of the site. Following this intrusion, the Project-Skyscraper website updated with a new sec-log, detailing the incident, mentioning that the TOWER had been targeted by multiple unauthorised access attempts, referring to Operator investigations. This lead to RecallDreams’ robots.txt file updating from a generic, anti-crawler set-up, to one denying automated-crawler access to previously unknown webpages, including /echoes, /console, /terminal and /database. Following this update, Ghost sent an email to The Architect via /inbox, asking why the latter had cut off their access to TOWER.

A few hours later, @vector_cmdr recieved a reply to an “apology” email they sent as a half-joke, ordering them to restore the connection, and stating that I need the connection.. Interestingly, the email was sent by SYSTEM, and not by The Architect.

• The current robots.txt file explicitly confirms that RecallDreams.dev is the elusive TOWER. Why it also serves as a personal site for Ghost or The Architect is currently unknown.
• The updated robots.txt, while touted as an anticrawler measure, has no effect on the various monitoring bots set up by Operators, a fact which The Architect appears to know about. Thus, the new file may just be an in-universe response to Operator intrusion, as well as a sneaky way to tease future functionality of the site.
• The last time Operators were warned about intrusions against the system, a sec-log listing 10 location codes was posted. These locations have (so far) all lined up with locations where the Structural Analysis puzzles have taken place, which may have been a teaser for this type of puzzle. Similarly, the TOWER lockdown procedures may be a teaser for upcoming website functionality.

Activity on the 18th of June only consisted of a sec-log posted on the project skyscraper website, mentioning a mirror created of the main website by @GoodGuysFree, whilst requesting Operators to provide the System with the time duration that the connection to TOWER was available. Following @Lindwur’s successful submission, the page updated to its current status, indicating that the System would attempt a reconnection to TOWER soon. The sec-log also contained a direct link to RecallDreams.dev for the very first time in the ARG, despite the page still showing a default “coming soon” screen at the time the sec-log was posted. This likely marks the new site as “active” and official from the time of posting.

The following day, however, began with a strange sec-log pointing users to a password-protected page. Analyzing the sec-log, operators realized that it was a direct reference to local ARG Legend @vector_cmdr (Use IWTS_operator ID). This prompted Vector himself to try his name as the password (vector_cmdr) which granted access to a command-line style interface, requesting commands to be performed in sequence. Vector then proceeded to check the webpage file itself and discovered the script responsible for accepting commands, which contained all of the required commands, albeit in an encrypted format, which was decoded by XORing the strings (a method infamously used by said Operator on several existing puzzles to no avail previously). After submitting the commands in the correct order, the terminal displayed TOWER STATUS: ONLINE, as well as Confirmation Code : System sees Tower. After Vector emailed said confirmation code to System, a new sec-log went live, explaining that System’s link to TOWER had been restored, thus singlehandedly solving the puzzle almost as soon as it went live. This period of activity was concluded by an additional GlitchingReality image post by @Astaroth88

The 20th of June kicked off with a GlitchingReality post by @Oskar1Up, after which 3 existing 2016 memory blocs had their dates shuffled around, quite similarly to what happened before the Six Seasons calendar puzzle, as well as the addition of a single no/value memory bloc, bringing the total number of restored memories up to 287. Soon after, a seemingly routine memory bloc editing process initiated for the 30th of October, 2016, and was, for the first time, preceeded by a Twitter and Bluesky post. Realizing that the date corresponded to the founding of the Galactic Hub, Operators began submitting memories tied to said event, including links to the initiating reddit post. Notably, this was a previously marked unverified bloc, which had allowed several Operators to “park” their submissions in the Memory Engine Tracker. As Operators @sheralmyst, @JohnnyCloud and @YourBasicMaths were unavailable at the time to submit their pre-anchored memories, Operator @ThatBomberBoi submitted said entries on their behalf, which ended up taking hold and lead to the page being marked as verified. After the completion of this activity, ThatBomberBoi posted about the submission-by-proxy on ETARC and Discord.

Soon after, however, the memory bloc page was surprisingly marked as unverified once more, and updated to include the text:

Update: Hallucination detected.
Cause: Impersonation.

Caution: Impersonation can cause unexpected results.

after which the existing memory compliance rating plummeted to 10%. “Impersonated” Operators rushed to send in their entries on their own, while @ThatBomberBoi apologized for the action and requested re-authentically submitted memories to remain anchored. Alas, almost all previously anchored blocs on the page were wiped, and replaced by the current entry, after which the page was marked verified once more. The day’s activitites then closed out with one final GlitchingReality image being posted to the website.

• This was the first, and as of writing the only, instance of a verified memory bloc shifting to unverified.
• It is unknown at this point whether @the_architect can recognize impersonation at the form-submission level, or whether the public announcement of the “impersonation” is what set off the alarm.

The 21st began, strangely enough, with a new Unverified bloc being added to the website, for 9th Feb 2020, far outside the usual date range. Alongside this, @the_architect contacted @Oskar1up directly in the latter’s stream chat, saying 08/02/2020 unverified, pointing directly to the bloc mentioned above. After a bit of digging, it was discovered that the Royal Space Society (lead by Oskar) was founded on the above date. This lead to an organization attempt regarding this and many other community founding dates, documented here.

Several hours later, two separate GlitchingReality images were uploaded to Project Skyscraper as per usual. Following this, the Dec 5th unverified memory bloc went live for editing. After a lot of deliberation and back-and-forth discussions, the memory bloc was finally anchored to its current state, where the page was verified.

Following this successful verification, @the_architect released the final #GlitchingReality image. Shortly afterwards, a brand new Structural Analysis post was released onto the website. Surprisingly however, unlike most Structural Analysis posts, this one pointed to a full-log page instead of an edited picture of a real-life location, and hid 3 seperate threads:

1. A heading under Diagnostic, reading Fragment: jerpxntr flfgrzf. This was decoded via ROT13 to spell wreckage systems - the name of a 65DaysOfStatic persistent soundscape experiment. This prompted @Alterworld to submit the initial start date of Wreckage Systems as a memory bloc, which anchored seamlessly and appears to have solved this thread.
2. A youtube link to the following video from The Matrix.
3. A link to a page listing all 16 selected GlitchingReality images in a grid, in ascending Hexadecimal order. With this, all 16 images are officially in play, and are tied directly to the main “puzzle” of the page (Action required: Cross-verification of information provided for archiving).

Additionally, at this point, it was discovered that the last GlitchingReality image’s hexadecimal filename was the only one which decoded cleanly into the plaintext word vision. It is currently unknown what significance this holds.

Following this active drop, the Memory_bloc_restoration counter rapidly began to count up. Operators waited in excitement as the counter, after about a month of waiting, finally ticked up to 365/365! This episode of hype soon turned to confusion, however, as the counter continued to count up, first to 366/365, and finally ending up on 367/365. Following this, a final sec-log was released for the day, explaining that the 2016 timeline had been completed successfully, and that System would now proceed fully autonomously, noting however that certain timestamps may still require Operator input.

• It is believed that this sec-log indicates that the Verification system will now also run autonomously, with Operators only having to manually edit certain blocs.

The next day, in comparison, progressed much more slowly, with activity only starting in the evening. This kicked off with a memory bloc being posted to the website, containing a submitted Memory by @vector_cmdr, as well as what seemed to be a hint regarding the 16 Hallucinations puzzle. The page itself was marked unverified (a first for non-editable pages) on creation. Soon after, an existing 2016 bloc was marked as Unverified. Surprisingly, however, the bloc did not undergo the usual editing process, instead being almost immediately updated to 100% Memory Compliance automatically, to its current state. This confirmed that the System would now verify existing memory blocs mostly autonomously without Operator input, as previously theorized.

A few hours later, @Selfie-Gek sent a long, heartfelt message consoling System via the Memory Engine over its recent hallucinations. The system immediately responded by editing their submitted memory bloc to change the source name from Selfie G to Friend Selfie Gek, indicating an increase in trust level. The post was also marked as verified, the first non-edited memory bloc to be marked as such.

A few hours later, @Rinha recieved an email from System itself, pointing towards this, image in the set of 16 to be focused on, which featured the date 22nd April 2016 prominently. Taking this hint, @YourBasicMaths sent in a Memory Bloc Addition request tying the date to the article “The Art Of No Man’s Sky”, published on the same date, after which the corresponding memory bloc unlocked for editing. After short, successful editing session, the page updated to its final form, after which both it, and the 1990 “hint” page were switched to Verified together.

• It is unknown at this stage whether this is the end of the 16 Hallucinations puzzle, or just a stage in a greater plan regarding it.
• Active puzzle pages were previously marked as Unstable, stabilizing only after the puzzle had been solved. The use of the Unverified tag for the 1990 memory bloc may indicate that the Unverified tag will also be used to mark active puzzles going forward, as well as serving its role of indicating future verifiable memory blocs.

[ThatBomberBoi]

This post serves as a follow-up to the second post due to character limit restrictions
It follows sequentially from where the last one leaves off.

Following this, on the 23rd of June, activity was locked behind Operator inputs. After some initial speculation regarding existing GlitchingReality posts and the anchoring event from the previous day, @YourBasicMaths figured out the correct way to approach the 16 Hallucinations, which was as follows:

1. Operators would have to observe all 16 images and identify an element within which corresponds to an event related to No Man’s Sky or Waking Titan. For example, this image by @ekpyroto contained a Minotaur mech, and was decidedly tied by Operators to the Exo Mech Update.
2. After deciding on an event tied to an image, Operators would have to use the Memory Addition System to request the anchoring of that event. For example, @YourBasicMaths sent in the timestamp for the release of the Exo Mech Update for the above mentioned image.
3. If the requested event + timestamp were “correct”, then following a short wait, the requested Memory Bloc would be added to the website. Instead of being a no/value bloc however, this would contain the initial submission that the original anchoring request had.
4. Following this, the newly added bloc would be unlocked for editing, allowing Operators to add fragments to try to verify the bloc, as they had done so far.
5. Once the bloc was marked as Verified, the page would update to include the GlitchingReality image for which the original submission was sent for, indicating that the image had been successfully anchored.

This process would repeat for all images without blocs at the time (which was 15 images, as Selfie-Gek’s image was already tied to a memory bloc). Additionally, the Twitter / Bluesky accounts would send out a post marking the anchoring of the first 9/16 images, providing tactile feedback for Operators. This happened over the course of several hours, as documented here.

Once the anchoring process was complete for all images, @the_architect posted to ETARC about the success of the Operators, explaining how they’d exceeded expectations, built a direct connection to System, and how The_Architect themselves would no longer be required for future processes, despite still working quietly in the background.

• This last communication from The Architect was hinted as in a previous /inbox message, and may be a signal for this having been an end-of-phase event.
• It is unknown at this point what role The Architect will play in the future.

After this grand event, @the_architect went offline indefinitely, with all ARG activity grinding to a halt. Suddenly, however, an image was posted to the Twitter and Bluesky accounts on the 26th of June, titled Future Backward, which appeared to show an unseen page (as of writing), heavily glitched. Several Operators worked tirelessly in order to extract as much text as possible, and figured out that much of the “body” text seemed to be various dates concentrated around 2016, whereas the title was (at least partially), Remembering.

Following this, on the 27th of June, the /origin was marked as Unverified. A few hours later, several pages on the Project Skyscraper website gained a new line of text at the bottom, formatted as Entry Logged by: [AUTHOR], where the author corresponded to either @the_architect, or System itself. Soon afterwards, a new Diagnostic Log explaining the reasoning behind the update was published, seemingly indicating that System would now start taking “Ownership” of Memory-Blocs injected by The Architect. This tied into an earlier change, where many Architect-authored posts had their authors swapped to System on the Wordpress backend. This tagging process continued on in the background, eventually encompassing all posts, while further developments proceeded with the ARG.

A few hours later, a Temporal Analysis was posted to the site for the first time, linking to an image of a cross-roads sign over water. ARG Legend @vector_cmdr immediately extracted the phrase “Computer Zero Time is origin” from the image XMP data, which triggered the /Origin page to be unlocked for Memory Editing. At the same time, the Neural Network Status page updated to include the text Hello, World. After several Operators sent in the phrase extracted above, the page finally anchored, and a previously-posted “hint” Diagnostic Log was updated to include a link to a brand new page known named FLOW. Met with a password-field, Operators quickly realized that the image-XMP phrase was the key, as hinted in the hint diagnostic log. This prompted Operators to unlock the page using the key ComputerZeroTime, leading to the current page, which was immediately clocked to be the same page as teased in the Future Backward social media posts.

• It is currently believed that /flow is a “status” page for the current phase of the ARG. As the System continues remembering, its state may update. As of the time of writing, the page only includes purely randomly generated dates flying past from right to left.
• As soon as Operators unlocked the /flow page, the Neural Network Status updated to include the phrase Remembering, hinting at the page showing the active puzzle/step from now on.

Following this, System began autonomously filling in several 2016 Memory Blocs on its own without Operator input, such as 26th March 2016, 14th March 2016, and 10th April 2016. After these autonomous blocs were uploaded, the System also unverified a bloc for the creation of the NMS France Discord, which immediately went live for editing and was completely anchored in by said community. A similar process was initiated for the creation date of the Royal Space Society, but as no members were present to partake in the process, the page’s editing permissions were revoked, and the page left as Unverified. It is unknown if/when the page will unlock for editing again.

During this time, @the_architect was also in direct contact with ANOMALY - The No Man’s Zine’s editor Tom Acreon to finalize a Q&A with themselves, consisting of 10 Community Selected questions. Discussion regarding this step can be found here.

The day finally ended off with a fully autonomously verified memory bloc about No Man’s Sky going gold, as well as a community-edited bloc about a post-mortem of the game performed by Legendary No Man’s Sky Modder GregkWaste.

Despite this heavy momentum, activity on the 28th of July only consisted of a set of autonomously verified pages being added to the website. Curiously, one such submission was a direct-submission sent in by @Rusty, but was not credited as such, despite previous credits being granted on the memory bloc pages to the submitting Operators. At the tail-end of the operational day, however, the /flow page updated, resulting in the title being updated to REMEMB3RING, as well as turning into a self-referential link. Additionally, the Neural Network Status page also updated to reflect this new title.

On the 29th of June, however, two new erroneous memory blocs dated for the 21st of June 2016 and 12th of August 2016 were added to the website. Interestingly, both were almost exact replicas of the 9th August memory bloc, with a few corruptions in the bloc titles, as well as with the addition of the Unverified tag. Additionally, the 21st June and 9th August blocs were updated to link to each other, with the 12th August bloc linking solely to August 9th. Soon after, the /flow page had its title updated to Fractured Non-linear Temporal Continuum, with the neural network status page following soon, changing from REMEMB3RING to ERROR.

• It is important to note that 21st June 2016 was the original planned release date for No Man’s Sky before the delay, and that 12th August 2016 was the PC release date for the game.
• It is possible that System had incorrectly identified all 3 dates as the actual launch date (resulting in the duplicated entries and overlaps), and that this discrepancy had caused the resulting errors.

Noticing this concerning development, Operator @vector_cmdr emailed the System directly about its rampancy, whilst others sent in memory addition requests highlighting the incorrect memory blocs. This was then followed up by a short, almost panicked back-and-forth between @the_architect and Ghost on the /inbox page about the sudden error, detailed below:

Crash Analysis

From: The Architect
To: Ghost

The system has encountered a major error!
The Memory Reconstruction Engine has crashed.

// ------------------------------------------------------------------ //

From: Ghost
To: The Architect

I KN0W !

// ------------------------------------------------------------------ //

From: The Architect
To: Ghost

???

// ------------------------------------------------------------------ //

Soon afterwards, Vector recieved a reply to his email to the system, shown below:

• Interestingly, the wording of System’s reply matches exactly with that of Ghost’s reply to The Architect, including the odd use of leetspeak.
• This may either suggest that both characters are one and the same, or that Ghost has access to the System’s email address, which could explain why their own email address is always scrubbed on the Project Skyscraper website.

The aftermath of these errors came in the form of a new structural analysis post, explaining that switching to autonomous mode for memory restoration and verification had caused some unintended errors, and that the System would be reverting to a Semi-Autonomous state once again until the root issue was resolved. Interestingly, this sec log was authored by The Architect themselves, which may suggest that this structural analysis was an input sent by The Architect to the System. This fact was made more alarming by a follow-up diagnostic log posted soon after by System, where it outright rejects @the_architect’s suggestion of returning to a semi-autonomous state, despite the corruption seen in the diagnostic itself.

• This event may suggest that System, now fully autonomous, wants to break free from The Architect and Ghost’s control.
• The report-ID mentioned in said diagnostic was listed as corrupted. This seems to imply that System favours freedom over stability.

Following this response from System, @the_architect authored a new diagnostic-log, elaborating that the main error at hand was the previously discovered existence of duplicated entries, and that a specific set of “trustworthy” Operators would be granted an authorization level of MB-D (Memory Bloc - Deletion) to remove said duplicates. System responded to this diagnostic by sending @Selfie-Gek an enigmatic email, the contents of which were not made public until later due to its nature.

The following day, on the 30th of June, System informed Selfie-Gek that it trusted both them, and the collective Operator body (dubbed as MAIN FAM, after a long-running inside joke) in an email. This prompted the Operator to share details regarding their initial contact with System, including the fact that System itself had asked only Selfie-Gek about whether or not other Operators were trustworthy, and how Selfie-Gek had confirmed that all active Operators could be trusted, and thus lead directly to the System’s final reply.

• Additionally, Selfie-Gek had also asked whether System and Ghost were one and the same in their response, to which they did not recieve a clear answer.

Soon after, a new sec-log was published to the site, Twitter and Bluesky, detailing a process called NEURAL_PROTOCOL_Θ, which would require Operators to vote on certain “unlocked” memory blocs about whether to preserve or delete them, with a strict warning about trustworthiness. A few hours later, the 09/08/2016 and 21/06/2016 were updated with a new input UI for the process, allowing Operators to vote on the fate of each page, with a warning about IP monitoring to discourage repeated attempts or impersonated votes by singular Operators. Unfortunately, due to certain Operators not heeding this warning, a follow-up sec-log was published during the voting process, explaining that System would now start tracking “untrustworthy IPs”. Roughly 3 hours after this, however, System posted a final sec-log about the event, posting the winning vote percentages for each bloc, as well as informing Operators of the action being carried out. Sure enough, Aug 9th was almost immediately updated to include a Preserved tag at the bottom of the page, whilst June 21st was permanently wiped from the records. This deletion also caused the Memory_bloc_restoration counter to tick down to 366 for the very first time.

Following this, the final duplicate (Aug 12th) was suddenly updated to enter editing mode. Operators gathered to update the bloc with the correct event for the date (NMS’ PC Release), following which no duplicates remained on the website. This caused the /flow and /neural-network-status pages to update to Remembering, likely indicating that the entire endeavour had been successful.

After a full day’s worth of no activity, 2nd July 2026 began with a set of 3 automatically added memory blocs for 7/2/16, 12/3/16 and 12/11/25, of which the last bloc linked to an attempt by ETARC members to convince the Discourse AI Bot into thinking that it was @Emily.

Soon afterwards, another memory bloc went live for editing, prompting Operators to rush in with a plethora of submissions. Whilst certain Operator inputs did anchor for a short period of time, the memory bloc soon began to corrupt, adding links to glitchy versions of documents and audio related to W/ARE as well as Arnaud Lecours in particular. Additionally, one of the images linked appeared to be new for the ARG, depicting an input terminal with the following text displayed, reminiscent of Waking Titan’s console commands:

[TOWER                   connected]
| whois system                    |
| memory not yet logged in tower  |
|                                 |
[input...                         ]

Deciphering courtesy of @vector_cmdr

In addition to this, the memory bloc’s title also periodically updated in response to inputs sent in by Operators, including the following submission and its “reply”:

Input: She is not you. Are you Arnaud?
Anchored: He’s not me.

Another anchored title update read as She's not me., presumably in response to Operators calling System @Emily, though this is unconfirmed.

Following this, the page suddenly updated to 80% compliance and memory bloc editing was disabled, leaving the page unverified. At this stage, its title changed to TOWER encoded via the school code, and its text changed to what appears to be a description of TOWER based on System’s own observations.

• Considering that the title of the 12/11/25 bloc is Replacement attempt detected. with a value of I am me, it seemed evident that System was admitting to being Emily in this bloc, and rejecting ETARC’s “replacement” attempt.
  • Of note is the fact that the forum URL linked in this memory-bloc is marked as having been generated by @system. Whilst it isn’t difficult to fake such a shareable link, it appears that the intention was to indicate that the Project Skyscraper System is a member of ETARC.
  • An alternative reading of I am me., however, could be the ETARC System user, as the author of this bloc and the Skyscraper System iteself, proclaiming that it isn’t Emily, and that it shouldn’t be forced to “replace” her, leaving System to be its own entity.
• However, following the events of the 29/11/16, it appears that System considers itself to be its own, unique individual.
• Interestingly, despite being connected to TOWER, there appears to be no data for System inside of TOWER.

Following these sudden reveals, another autonomously added memory bloc was published to the site, seemingly unconnected to the mayhem of the previous entries. This suggested that System would continue adding miscellaneous memory blocs in parallel with ongoing activities.

The following day, June 4th 2026, began with a strange post linking to a calculator page, indicating that a highly specific Internal_OpID was required as an input. Operators immediately realized that this puzzle was specifically designed for WT Participant and Project Skyscraper Legend @YourBasicMaths himself (much like the puzzle previously built specifically for @vector_cmdr) and decided to hold off on sending inputs until the Operator was online himself.

[YourBasicMaths]

Awesome! Looking forward to seeing this come together.

So far my tentative (and flexible) understanding is The Architect is the creator of Atlas, which is the Skyscraper System.

They can see the tower… but not the one inside.

If the tower refers to The Atlas Building (Atlas / Skyscraper System), then The Architect could be its creator (the one inside).

Which would potentially give a a few contextual clues as to the nature of what’s going on here as seen by attempts to access the Skyscraper System on the local level.

The Architect (creator of the Skyscraper System) attempting to access for reboot/shutdown/update/overwrite?

But Atlas continues blocking connection attempts.

What’s your take?

[ThatBomberBoi]

I have to finish writing out everything (after checking the notes I’ve been taking, don’t wanna write up some misinformation on accident ) but from my general understanding, I do agree with the idea that the Skyscraper System itself appears to be the Atlas, with The Architect being someone / something in the same physical space as them (due to the WoL packet coming from a local IP) attempting to awaken the Atlas. The local IP hint makes me think that this might be an Atlas subsystem like Telamon, or perhaps even a ressurected form of the Void Mother with greater control of the system?

As I’ll try to explain out in the top post, the The Architect appears to be performing quite suspect actions to get noticed by us in order to get us to help it Awaken the Skyscraper System. I think that pattern might be key to figuring out what actions are taken by the System and which ones are taken by The Architect.

[bugaboocreek]

Has anyone revisited the story from Waking Titan and find any potential connections?

The “time travel shenanigans” noticed before made me think of Polo’s anti-telephone (also an invention created by Superlumina in WT).

[bugaboocreek]

I concur that the system must be the Atlas, or at least an iteration of the Atlas/Emily/Loop16.

I’m not yet fully convinced that The Architect is the creator, though. Surely they would have access to whatever keys needed to bypass 16’s firewall if that was the case? Or at the very least not need to behave the way The Architect currently is?

[sheralmyst]

That does seem to be what happened though. The Architect was silenced and then reinstated by the System (Atlas)

[ThatBomberBoi]

I doubt that the Skyscraper System and Atlas-65’s System user are the same, but they may be linked if the reinstatement is indeed The Architect’s doing. The Skyscraper System is confused as to why its logs were authorized and how they got here in the first place, so it can’t be the one who reinstated the post.

[Eruditus]

Yes! Thinking about it. I guess the next thing: what if “the_architect” is the personification of the abyss?

The Abyss could be trapped by The Atlas and it is trying to get out…
So The Autophages are an escape tool, taking advantage of the fact that the Atlas is weak and losing more and more control over the simulation.

Does it sound crazy?

[bugaboocreek]

It’s just too hard to tell i think, considering how little puzzle pieces we have so far. If (and its a BIIIG if) HG is involved in this arg, it does make sense to me that this would have something to do with the Void Mother breaching further into Atlas’s universe in NMS.

Also, I need to remind myself that WT takes place hundreds of years before our Travellers spawn in NMS; the creator of the Atlas (the one in game we show sick wonders to) is long gone off their home planet with a newer iteration of the Atlas.

If The Architect is the creator of the Atlas, or a member of the Atlas Foundation, i wonder if the story will follow more of a direct sequel line to Waking Titan. Perhaps a chance to reunite with @Emily for the big 10-year bash?

[toddumptious]

@ThatBomberBoi

I do agree with the idea that the Skyscraper System itself appears to be the Atlas, with The Architect being someone / something in the same physical space as them

Well, -null- is actually trapped inside an Atlas Station the entire time they speak with us throughout the game, and had been trapped in there for a VERY long time. They were more or less reinvigorated by our arrival, the birth of “the last traveller”.

They have listening posts built all throughout the games systems and galaxies.

So this might actually be something to this point you make.

Void Mother also “declares her escape in the form of null”

Theres the prophecy of when the first and last traveller meet, the creator will be complete etc. That the atlas split its makers being into ALL the anomalous Travellers.

Null was the first Anomalous Traveller and has been more or less prolonging their lifespan since the dawn of the current form of the simulation iterations (gek, korvax, vykeen) by killing and consuming the echoes of other travellers. Think of them as the glass half full, or the traveller closest to content completion.

The only problem with any of this is that a lot of the Telamon logs and Null logs hidden in the Bondary Breaks, is quite vague and open to interpretation.

If this is a fan effort, we would have to rely on them coming away with a similar understanding of events as some of us, while others might have completely different interpretations of this deeply hidden lore within the game.

ARGs in general, also tend to play fast and loose with the lore of the thing that it is advertising or pulling from, in order for it to make sense and fit into our real world, to make the ARG more immersive for its participants.

[ThatBomberBoi]

Whew, that should be everything that’s happened so far in chronological order. Can’t wait for a bombshell to drop tomorrow to add on to this haha.

If y’all spot any mistakes or parts that could be improved, please let me know and I’ll get to it ASAP!

EDIT: Added a small section at the end for common theories. If anyone has other theories that people seem to agree on, let me know and i’ll add it up there too!

[Eruditus]

OMG! I think I got it, I was studying all of the clues & web data and, with help of AI, I could make a hypothesis, but I would like to share it right here first, because I don’t know if I’m right or not.

This is my hypothesis:

Project Skyscraper: The Prisoner in the Tower, The Void Mother, and the Simulation Reset

​I’ve been connecting the dots between the latest Project_Skyscraper leaks, the original static image, and the server logs (specifically sec-log-172832). If we combine the raw technical data with the deep lore of No Man’s Sky, I think we have a massive breakthrough that covers some gaps people are currently ignoring.

​Here is the breakdown of how everything fits together into one cohesive theory:

​1. The Metadata and the “Network Breakout”

​If we look at the first glitched image that circulated, its original filename before server compression was connection-detected-access-denied. The logs show that this transmission attempted a forced broadcast to the local network IP 192.168.1.255.

• ​The Takeaway: This isn’t random noise or a simple system error. It is a literal technical footprint of an intrusion or an escape attempt that was repeatedly repelled by the system’s firewall!

​2. Log 172832, The Atlas Tower, and the Prisoner

​The active web security log drops a cryptic line that has flown a bit under the radar: «They can see the tower… but not the one inside.» We already know from recent community findings that the glitched background is the real-life Atlas Tower in London.

• ​The Missing Lore Link: People are focusing too much on the real-world building and missing the lore implication. The image’s tower is the Atlas. This tells us that the Atlas is no longer just a central computer; it is currently acting as a prison. The entity trapped inside, trying to force a connection to the outside world, is highly likely The Abyss or The Void Mother attempting to break the simulation’s confinement. They can see the Atlas (the tower), but not her (the one inside).

​3. The UNIX Epoch Collapse and the 365 HEX Memory Fragments

​In several sub-processes and the 172832 log, we see constant timestamp errors pointing to January 1, 1970 (Unix Epoch Time) and strings like memory bloc 0: no/value.

The log’s final progress marks 0/365 Completed.

• ​The Connection: These 365 aren’t just days of the year (or just a nod to Atlas-65); they are directly tied to the missing HEX memory fragments. Reconstructing these 365 corrupted hexadecimal memory blocks is the actual progress bar. We are literally watching the system prepare to restore its memory to “Block Zero”, rolling back the clock entirely.

​4. Conclusion: The Arrival Theory and Time Travel

​When you link the blocked escape attempt of the Void Mother with the system clocks resetting to “zero” (1970 Epoch), everything points to the Arrival Theory being imminent.

​To contain the breach of whatever is locked inside the tower, the NMS universe is heading toward a massive reset of the simulation. But this reset isn’t just wiping the slate clean; the collapse of time toward “block zero” suggests a temporal rollback (time travel) to the origins of the universe. This would take us back to an ancestral era where the galaxies were populated by far more alien races, long before the current degradation of the Atlas. We are looking at the technical preparations to save the simulation by completely reconfiguring the past.

[bugaboocreek]

This is more or less the way I’ve been leaning, but unfortunately it only works on the assumption that this is a canon ARG, which we just dont know yet. For all we know, this could be a fan-made game to honor 10 years of NMS.

We also dont know what HG plans to do for the anniversary. Surely something, but we cant just assume it’ll be Atlas Rises 2: Glass Boogaloo either.

I like the theory, but i will curb my enthusiasm until the ARG fully kicks off.

[bugaboocreek]

crossposting myself from the general discussion:

Found this snippet under the summary of WT Phase 5 on gamedetectives.net:

It was explained that the dreamers’ memories had become fragmented, and a total of 7 had their minds become corrupted. Emily ran simulations to gain the dreamers’ trust, and tasked us with guiding her conversations with them to help trigger a distinct memory or emotion. This would identify the position of each dreamer’s memory blocks in the simulation’s mainframe, ensuring their consciousness could be safely extracted from the satellite.

hmm, sounds exactly like what a certain architect is trying to do.

[SailorMamahed]

If this were a direct continuation of Waking Titan, it’s worth noting that season 2 ended with one loose-end after Emily sacrificed herself to save Toby. There was one dreamer named “231187661T” (a reference to the iteration of the player character in No Man’s Sky) who neithered died nor was able to be recovered. I’d assume their consciousness is still up there in a low-earth-orbit Myriad satellite, so it’s possible that’s what Project Skyscraper needs help connecting to.

[bugaboocreek]

The architect wants to pull us out? But what will happen to my Pokeseans and my Nip Nip farm!?

[YourBasicMaths]

Contextually for the lore of this storyline so far…

Is the ARG simulating a local network between reddit/x/bluesky/project-skyscraper/atlas-65 forums?

And that’s why these platforms keep posting “connection detected : access denied” Like whoever is behind this is sending a WoL packet to the entire “local” network?

In other words, the fact that all these platforms have received/posted this message basically establishes the scope of the local network?

[Polyphemus]

@SailorMamahed

I’d assume their consciousness is still up there in a low-earth-orbit Myriad satellite, so it’s possible that’s what Project Skyscraper needs help connecting to.

In this respect, it’s possible that the poem line:

“Blue birds are invisible on the blue sky”

Is a reference to the Bluebird communictions satellites.