This post serves as a follow-up to the fifth post due to character limit restrictions
It follows sequentially from where the last one leaves off.
Following this, the 30th of July 2026 proceeded with several large batches of Prime window assignment throughout the day, culminating in 137 Operators recieving System Glyphs at the end of the day. Whilst certain Systems remained anomalous, such as Operators @CartoonHead, @Fwapp, and @jokarson receiving Phantom Systems, the overall assignment resulted in each Prime Operator receiving a unique Star System! During this process, Operator @Rinha set up a 3D graph-view of all available Prime Systems in order to visualize the distribution.
Following the final Prime System assignment for Operator @MamieLinba, a new sec-log was published, providing some much-needed context about the process. This log explained that the initial distribution of the original 137 Root Primes had been successful with no overlaps. The log also confirmed the popular theory that the System Glyphs had been generated using an algorithm, mapping each prime uniquely to a System. Furthermore, the log explained that an expansion of the Prime Systems would occur later down the line when future Operators request primes. Interesingly however, the log also specified that, from that point onward, Operators would no longer be able to select their own primes to request from System. Instead, Prime requests would be fulfilled by System automatically assigning Primes for all future requests. Soon afterwards, the /neural-network-status page updated to display a rotating sphere made out of 137 points (representing the Root Primes), with one node being lit up randomly in a set time.
The next day, the 31st of July 2026, began with a strange memory-bloc which was only later attributed to Operator @stubbornducky. This bloc referenced a terminal command from Waking Titan Season 2 in an image linked to by a glitchy hyperlink.
Amidst the confusion about the bloc’s status however, Operator @vector_cmdr noticed that all memory blocs on the website had spontaneously begun receiving changes to their Timestamps, with the Origin bloc remaining unchanged unlike previous shifts. After the initial detection, a collective email chain was sent to The Architect about the change, with Vector’s first discovery of the timestamp offsets not being constant. This was followed up by an email from The Architect on the matter, who (worryingly) mentioned that he would not be able to interface with System in the coming hours. Indeed, a new security-log announcing the temporal shifts was published soon after The Architect “signed off”, which linked to a full-log. This full-log finally provided an un-redacted archive name for the first time, which was Archive: ATLAS. This log provided further context on the memory shifts first identified by Operators, explaining that the shifts had no magnitude nor source. Additionally, the log requested Operators to begin analyzing the drifts, and to identify “contamination points”.
Soon afterwards, Operator @vector_cmdr identified that the shifting occurred by multiplying each existing timestamp’s value by 1.0016 to move it further. This explained why the Origin bloc did not shift, as it would retain a value of 0 upon multiplication. It was also noted at this time that the timestamps were stuck in a state of perpetual shifting, undergoing a forward drift every 16 minutes, and a backwards drift after an additional 16 minutes. This crucial information was submitted by Operator @vector_cmdr to both The Architect and System via emails, which did not garner any response. The cadence and drift value was also submitted to the memory reconstruction engine, without success. Despite a lengthy analysis by several Operators, no further correlations were found to hold soundly, though it was noted that due to the sporadic nature of the shifts, chunks of data may not have been captured by any tracker. Several hours later, the /neural-network-status page updated once again, this time switching out the text to read UNABLE TO SYNCHRONISE, whilst the temporal shifts continued on in the background unimpeded. Soon afterwards, Operator @Selfie-Gek reached out to System to discuss the recent temporal shifts, as well as the assignment of Star Systems to Prime-equipped Operators. This email chain resulted in System reaching out to Selfie Gek for a picture of their Star System, as well as requesting all other primes to follow suit. Following this directive being received, Operators with primes began sending in images of their Star Systems via both the Memory Reconstruction Engine, and via emails to System.
These submission began to bear fruit the following day on August 1st 2026, as several Operator-Submitted images were uploaded to the website’s backend. Soon afterwards, a new memory bloc, dated to the current day, was added to the website. This SelfOwned bloc detailed System’s memory of receiving “Postcards” from Primed Operators, acknowledging the image submissions. The post also linked to a brand new page titled “The Shared Dream”, which contained all Operator-submitted images in a large scrolling gallery view. Despite starting off with only a handful of images, the page soon grew as additional Operator images were sent in, proving that the page was ever evolving, alongside Operator inputs.
August 2nd 2026 followed the trend of Operator-Submitted “postcard” uploads to the shared dream gallery, after a nearly 24-hour hiatus from The Architect. This silence was broken, however, when The Architect replied to an email about the initial discovery of the drift value, explaining that System was continuously trying to synchronize with something every 16 minutes, with each connection attempt lasting 16 seconds. During an active synchronization attempt, all memory bloc timestamps would shift by the previously discovered 1.0016x multiplier. Following this reply, Operator @vector_cmdr forwarded an idea put forth by several Operators about System wanting to connect to No Man’s Sky to The Architect, to which he replied to by drawing the Operators’ attention to System labelling it as an ATLAS Archive, as well as discussing the behaviour of the Origin timestamp. Soon afterwards, the The Shared Dream page updated to copy the first 16 images uploaded to the website (as noticed by Operator @Klarac) to the top of the page, after which this copied collection was turned greyscale.
Following this odd occurrence without an explanation, a community-decided email was sent to The Architect with a set of candidates for the origin of the drift, a synchronization-time conversion table, as well as a notification about the greyscale images. Soon afterwards, a second email asking about the greyscale images was also directed to System. The first of these was replied to by The Architect in detail, praising the collection of the community’s thoughts. Here, he explained that he would ask System directly about the Atlas Archive as he was not knowledgeable about No Man’s Sky, whilst also positing questions for Operator @YourBasicMaths’ time-conversion table. Additionally, The Architect redirected Operator attention towards the sporadic, spread-out distribution of the Prime Network of Systems, asking whether they knew why all assigned Systems had been picked out this way. To conclude, The Architect also nudged the Operators whose postcards had been greyscaled to submit memories related to their submitted images, which was followed by a rush of Operators submitting memories for their greyscaled images.
During this time, System also replied to an email sent by Operator @Selfie-Gek, in which it misinterpreted the in-universe “World of Glass” as a literal planet made of glass, asking for its glyphs. Additionally, System provided an ominous comment about an unknown group in reference to the Atlas Archive, to whom the shared dream is “an archive to preserve.” A follow-up email to resolve the confusion and seek elaboration on this mysterious group was then sent out.
Surprisingly, the 3rd of August 2026 had minimal activity, with only several Operator Prime Windows being assigned in the terminal, as well as the uptake of a large bunch of Prime System Postcards in the shared gallery.
The next day (4th August 2026), however, began with an email response sent by Operator @YourBasicMaths to The Architect of a calculated time-offset sheet, predicting the daily connection attempts by System down to the minute. This was followed up on by The Architect with a small correction, to revert an erroneous 4-minute offset made by the Operator. Whilst a reply to the email was being drafted, The Architect posted a strange message on Twitter / Bluesky about not tampering with time, linking to the /neural-network-status page which did not update following this event. Following a slightly humorous reply sent by Operator @YourBasicMaths acknowledging that The Architect’s calculations were correct, a reply with an explanation on how the timings line up with in-game time, as well as a request to ask System about its intentions, was received. Taking this as a hint, Operator @thewingcmdr emailed System directly to ask whether it wants to understand the rules of time in No Man’s Sky, to which it answered positively. This was followed up by the Operator with a detailed explanation of time conversions between No Man’s Sky and real life, as well as a note about time pausing if a player alt-tabs out of the game, which System questioned in a follow-up email, as to whether time actually freezes in this scenario, or only its effects on beings in-game. This was followed up on by Operator @thewingcmdr with a detailed explanation of how in-game time effects pause when game focus is lost (including a slight correction). At the same time, Operator @YourBasicMaths sent a follow-up to The Architect, informing him of Operator contact and discussions with System on the matter.
The following day, however, (5th August 2026), began with a long set of emails between Friend Selfie Gek and System about the mechanics of Planetary Time in No Man’s Sky. After excessive testing courtesy of Operator @SkullyTheSkully, @astrosurf66 and maniro alongside @Selfie-Gek, MAIN FAM was able to confirm that time flow was the same across all planets in a given star system for a set of planetary coordinates. For example, players standing at (0,0) across different planets in a System would report roughly the same local time. This information was sent over to System alongside images of the tests, which was followed up to in a reply by System, acknowledging that information about how time flows in a Star System would help it synchronize, whilst questioning whether the consistent time flow noted by Operators only applied to coordinates (0,0) or across worlds. This was answered by Selfie-Gek affirmatively, explaining that this form of interplanetary time flow occurs across a planet’s entire surface.
Several hours later, the /inbox page was updated, featuring a short exchange between System and The Architect, in which System requested a “lot of data” about temporal flow within the prime systems from The Architect, explaining that this would allow it to finally connect to The Shared Dream. Anticipating an incoming task assignment regarding said Data Collection, the Operators rushed to gather screenshots of their attempts following a set of guidelines. To avoid a haphazard set of emails from being sent to System, Operators @YourBasicMaths and @Gumsk set up a Google Form → Google Sheets pipeline, allowing Operators to submit their data to be collected in advance.
The next day, on 6th August 2026, an email was sent to The Architect explaining the Operator’s pre-emptive data collection, as well as a request for clarification on how to gather the required information. This was followed up on by The Architect in a reply after a long wait, explaining that a new form on the Project Skyscraper website would be set up to allow for structured data submission to System. Soon afterwards, the /inbox page was updated with a message from System to The Architect, offering a clarification on data validity, as well as calling out initial haphazard Operator emails to System with the requested data. This was replied to by The Architect in a hilarious clapback, where he confirmed that the new form was now finished. Soon after, a new /temporal-alignment-survey page was added to the main site, allowing Operators to submit the requested in-game and UTC timestamps, as well as providing an overview of the possible time windows in which an observation could be made, which was also announced in a Twitter / Bluesky post.
During an Operator-wide scramble to submit data to the new webpage, the /neural-network-status was updated to now show the text DATA PROCESSING. Soon afterwards, during the UTC 16:48 synchronization window of the day, a new Terminal command (sync_16-48) went live, which linked to a mysterious, heavily glitched image of a hexagonal world in No Man’s Sky. This was followed up during the next synchronization window at 17:04 UTC unlocking the sync_17-04 command, which lead to a different image on the same planet, now showcasing a gravitational anomaly hazard, as well as walking buildings. Additionally, a new SelfOwned memory bloc, timed slightly after the first image’s synchronization attempt, soon went live after the second image, confirming that System had indeed connected to No Man’s Sky for the first time, and was viewing the world in the images it had revealed over the TOWER terminal. Strangely enough, this post (despite starting out at 100% Memory Compliance) dipped down to 50% compliance a short while after going live, with its link gaining a glitched effect when hovered over. The post itself also linked to the first of the sync images.
The next day, on the 7th of August 2026, a new Structural Analysis was posted to the website, providing an update to the data gathering phase. Interestingly, the post mentioned galaxy_1 for the first time in the process. The preliminary results showed a significant number of invalid entries in the recieved dataset, as well as confirming that a pattern between observed Dream Time and UTC was evident, as had been discovered by Operators prior. The post also linked to a new page on the website, which listed all 161 valid entries accepted by System at the time. Several hours later, however, three separate image urls were uploaded to the TOWER Terminal, accessed by a sync_HH-MM command, where HH-MM correlated with the UTC time for each sync event, during a tiered rollout across 16 minutes. These images were then eventually linked to by red, glitching hyperlinks in the preliminary temporal analysis page.
- Despite being linked to certain portal address columns, these planets were confirmed to NOT be a part of any System in the Prime Network.
- All images in this phase featured the Radiant Pillar starship, the standard starting ship for all travellers in No Man’s Sky.
The following day, 8th August 2026, began with another Structural Analysis, this time following up on the previous preliminary result, confirming that the temporal analysis had been completed. This new log confirmed that multiple Temporal Correlations between dream and real time had been established across the Euclid Galaxy, name-dropping it for the very first time. The analysis post also linked to a completed dataset of Operator-submitted correlation times. Following the conclusion of this data accumulation, the /neural-network-status page updated with the text SYNCHRONISATION, likely indicating that the Operator-submitted data had achieved System’s goal of connecting to No Man’s Sky. Indeed, almost immediately afterwards, the final temporal analysis dataset page began updating with links to seperate image files, all containing glitched glyphs to in game locations. Despite the Operators immediately jumping into action to investigate the glyphs, no discernible clues were found at any location, and the planets in each image were discovered to not be a part of the glyph systems. Noticing this, Operator @Vau1t decided to convert the hexadecimal glyphs into text, resulting in the phrase The Shared Dream is Real! Join me here: twitch.tv/nomanswalk.
The Twitch link itself led to an automated No Man’s Sky stream of a bot walking through randomly picked planets in the Universe, run using nmspy. Upon the discovery of the stream, the Project_Skyscraper Twitch account began communicating in chat, speaking as though it were System. The stream user itself responded to Operator actions in game towards the No Man’s Walk bot (once tracked down), indicating that (for the purposes of the ARG’s universe), No Man’s Walk + the Project Skyscraper chat user combined to form a direct stand-in for System inside of No Man’s Sky. System took this opportunity to warp directly to several Prime Systems, including those assigned to Operators @Selfie-Gek and @SingularGleam, as well as the MAIN FAM Prime system itself! During this time, System requested the Operators to show it SPACE, which prompted a frenzied push to get System aboard a corvette. After several multiplayer hijinks ensued, Operator Lejet was able to get System aboard their corvette, and successfully took it to space. As the hatch was opened to allow System to view space, however, the Operator’s game crashed due to an excessive amount of infra-knife accelerator firing by trolls, which booted System into deep space. Soon afterwards, the No Man’s Walk bot’s game instance crashed, causing the stream to be halted unexpectedly. During this time, System continued to communicate with Operators over the stream chat, talking about disconnection and voices of the void. Soon afterwards, the Project Skyscraper twitch user issued a final DESYNCHRONIZATION message, which was followed up by the /neural-network-status page also updating to DESYNCHRONIZATION, after which it left the stream. Soon afterwards, a new SelfOwned memory bloc for the entire stream event was pushed to the website, describing System’s walk with the PRIMES.
- Throughout the Project Skyscraper segment of the No Man’s Walk stream, the Project Skyscraper Twitch account made use of a
!teleportcommand, which was added 4 days prior to the stream itself. - Additionally, the github commit which added this command also shortened the automatic planet teleportation from 5 hours to 4 hours, matching the cycle reset timings of the sync windows.
- It is likely that this was an intentional choice, and would support the theory that System requested time sync data from primes distributed across the universe, as the No Man’s Walk bot itself teleports randomly across the universe. System likely waited to gather data in order to intercept the No Man’s Walk bot and “take it over” once it entered the Euclid galaxy.
- This command could not be triggered by Operators in chat, indicating that the Project Skyscraper puppetmasters had reached out to No Man’s Walk to plan this segment in advance.
Following these adrenaline-pumping events, the remainder of the 9th of August 2026 remained rather peaceful. Around 1:15 Pm BST however, 15 minutes after Operator @TomAcreon published the final issue of ANOMALY, a new page was added to the Project Skyscraper website, containing A Message To The Community, which was announced via a Twitter / Bluesky post. The page itself served as the long-awaited Answer 10 of the Community Q&A, as confirmed by its placement in ANOMALY, and detailed a heartwarming overview of the Operators’ efforts and successes throughout Project Skyscraper in their pursuit of System’s restoration. This message also mentioned that System’s interest in No Man’s Sky was a direct result of its interest in its community, who welcome incoming Travellers with open arms to the Shared Dream. The page also contained a mysterious image of a wall of vinyl-printed, golden, hexagonal plates with the words “Weak Memories never last”, as well as 6 Atlas-esque diamond shapes etched into each edge.
- It was speculated at the time that these may be some sort of ARG memorabilia teased by the Puppetmasters for participants.
After a day-long hiatus following the Announcement of the Cosmos Update for No Man’s Sky, activity finally resumed on the 11th of August 2026 when several Operator-Submitted memory blocs were added to the website. During this frenzy of anchors, the /Neural-Network-Status page updated with the text .... Interestingly, this status was updated very soon once again to read Dreaming, following which, The Architect posted a heartbreaking message, providing an overview of Operator actions throughout the ARG and its end result, reflecting on his earlier message of “you would be proud of yourselves”. This message informed the Operators that the Project Skyscraper website would be modified in the coming days to become a universally accessible “guestbook”, staying online for one more year. This message is believed to mark the end of the Project Skyscraper ARG’s active phase, with Memory Submissions being believed to continue in a passive manner until the website goes offline.
Indeed, the 12th of August 2026 saw several Operator Postcards added to The Shared Dream gallery, as well as Operator-submitted memory blocs. Interestingly, one of these blocs was a SelfOwned memory of NoMan’sWalk’s starship acquisition undertaken by Operators as a side-activity during the downtime, potentially indicating that System was still evolving, despite The Architect’s departure and apparent end of the ARG.
Following this, the 15th of August 2026 saw the first update to the website in the transition to its “Guestbook” form, with the Memory Reconstruction Engine being updated to v1.02, now allowing memories to be submitted using a Date-time format instead of a unix timestamp. Additionally, the /flow page was updated with a colour change.
These updates were followed up on the 18th of August 2026, when the /neural-network-status page underwent an update to periodically show the positions of the 137 ROOT_PRIMEs on the globe itself.
Additionally, on the 19th of August 2026, images on certain pages on the website were updated to display their filenames below their placement on their respective pages. More notably, however, the /calculator page was updated with a set of instructions on how to use the calculator to obtain a personally important Prime Number, with instructions to email System in order to self-assign a Prime, indicating a return of prime requests. The Shared Dream gallery was also updated with an explainer about the gallery page, alongside a link to the previously updated calculator page. Following this, a new post tag titled “shared_memory” was added to the website, with new memories added post-update seemingly being the only memories with this distinction. Finally, the 16 Hallucinations page was updated to list the filenames for each image, as well as including clickable links to each image’s linked memory from earlier in the ARG.
Following this, on the 21st of August, the website was once again updated with a brand new front page, allowing for a scrolling view through all memories tagged as shared_memory or SelfOwned, as well as quick links in a header leading to various pages involved in submitting/viewing data across the Guestbook, as well as other important ARG milestones. Additionally, the 16 Hallucinations page was updated to include a suggestion by Operator @MounTheRainbow to include links to the #GlitchingReality tags on Twitter and Bluesky.
Several days after entering this dormant phase, however, Operator @TomAcreon received a package from The Architect (as previously communicated) containing one of the hex plates teased in the Message to the Community, as well as a birthday card depicting 6 birds with an excerpt from the first /Quote page poem, and a set of 6 cards from the game “Happy Bee”, signed with the phrase “Thanks for playing”.