đź“ť Project Skyscraper - Timeline / Storyline Thread

Project Skyscraper
160

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.
5 Likes