Project Skyscraper - Storyline / Narrative Discussion

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.

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 sake of clarity, I will be referring 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.)

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. Its 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 recieved 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 recieved 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 unintenionally 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 player 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, participants 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).

Running Theories

Note: This section contains assumptions and theories and should NOT be treated as canon until proven otherwise

  • Going off the assumption that The Architect is attempting to connect to the Skyscraper System, their haphazard posting and behavior may be intended to get us interested in Skyscraper itself, aiding The Architect in their attempts to connect by potentially overloading the system.
9 Likes

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?

5 Likes

I have to finish writing out everything (after checking the notes I’ve been taking, don’t wanna write up some misinformation on accident :sweat_smile:) 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.

4 Likes

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).

1 Like

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?

2 Likes

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

5 Likes

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.

3 Likes

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?

1 Like

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?

3 Likes

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.

4 Likes

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!

7 Likes

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.

1 Like

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.

3 Likes

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.

3 Likes

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.

4 Likes

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

3 Likes

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?

3 Likes

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.

6 Likes

In the interest of searchability and for quickly referencing stuff from in-game lore I thought I would share these with everyone here…

I was working on story docs for NMS over a year ago.

I had split most of them into seperate documents, but had yet to finish curating them all.

What I’m sharing below, was the dump file I created, that I was then pulling bits out of to make stand alone compendiums. So bare in mind, this is a 680 page mess of a file but it IS structured.

This is my main story DUMP file, it contains all the lore and logs (boundary breaks for Telamon and Null, crashed freighters, derelicts, abandoned buildings, Base NPC missions and the main artemis story plus trace of metal, etc etc).

Everything is also chaptered for quick scrolling via the left side chapter pane. I believe I did this before In Stellar Multitudes was added so I am missing that.

I thought it would be a useful source for those here to pull from. It does not contain the vy’keen/gek/korvax/Autophage ruin/monolith lore, as they were being worked on in a seperate dump files.

I think I may actually get around to finishing these some day soon. There are still a lot of <> brackets in place in the story dump that are usually the last thing I remove when I’m sure everythign is formatted correctly.

While the above is the main story dump masterfile I was pulling things out of, there is a smaller 141 page version of Atlas Rises here that contains the rememberance terminals as well as the Telamon/Null boundary break terminals, that some might find lighter on their devices/bandwidth

Atlas Rises

I also have, completed and finished, documents of the Expeditions that contained some lore which you may also find useful. I will post those shortly and add them to this post.

Expedition 10: Singularity
Expedition 11: Voyagers
Expedition 12: Omega
Expedition 13: Adrift
Expedition 14: Liquidators
Expedition 15: Aquarius
Expedition 16: The Cursed

The Autophage Lore (not fully formated/organised, but 100% contentcomplete)

Special note about this Autophage file… anywhere there was code for a randomised name, I did a find & replace with Em1l6y, since I was making these for the AtlasCSD forums and inserting our shared heritage. There are also a lot of <> brackets as I was still not done reformatting this one from the games LangFiles.

We have been invisible and quiet to the NMS community for a long long time so @AdaRynin started the running joke that we are the Autophage of the NMS community, a shared affinity with our robotic chums. You gotta scan to find us hiding and being chill and reclusive :wink:

Also of note, particularly with some Expedition stuff, if the game was requesting to do xx of xx, I usually replaced those numbers with silly things like 19 of 16 etc, or 1,616/1,919

If people would also like the korvax/vykeen/gek lore dumps that I had not formated, I guess I can share those too but I really don’t see them being all that important to the plot of the nature of the NMS simulation. Except maybe the odd Korvax/Gek First Spawn colossal archive that gives you an insight into stuff about Korvax Prime etc

Special special SPECIAL thanks to @DevilinPixy who provided the guts of the langfiles for these that I worked from back in 2024 as well as @Dragonsire and @ThatBomberBoi who routinely posted the Expedition langfiles and Icons on this forum for us as they came out. This would never have been possible without their help <3 <3 <3

19 Likes

(post deleted by author)

2 Likes