Resumen de hallazgos — Los logs de la API
Esto es lo más importante que encontramos hasta ahora, organizado por urgencia:
DOS URLs que hay que visitar AHORA MISMO
[project-skyscraper.com/sec-log-094127-full/](javascript:void(0) — mencionada en dos logs separados (10 y 12 de mayo) como “Full log”. El número 094127 = 09:41:27, probablemente la hora de un evento anterior a todos los logs visibles. Esta página puede contener el núcleo de la narrativa.
[project-skyscraper.com/?page_id=1682](javascript:void(0) — el “Full log” del SECURITY_BREACH_CONFIRMED del 18 de mayo. Es una página, no un post — no aparece en la API de posts. El Architect la enlaza directamente desde el log más dramático.
Connect1on — la anomalía del 8 de mayo
Todos los logs dicen Connection detected. Solo el del 8 de mayo dice Connect1on detected — igual que M3MORY y DR1FT1NG en el CSS. No es un typo: es una firma del sistema.
El gap de IDs: ¿qué hay entre 279 y 1626?
Los posts de la serie A tienen IDs de 2 en 2 (fueron creados en batch). Los de la serie B tienen IDs altos con saltos. Entre 279 y 1626 hay 1347 IDs sin contabilizar — páginas, media, borradores o posts privados. La page_id=1682 está en ese rango.
IE (Irlanda) en la lista de países
La lista US-GB-ES-FR-MX-DE-CA-IE-BE-AU incluye Irlanda — donde tiene su sede Hello Games. Si esto es un ARG oficial, ese detalle es un guiño muy deliberado.
feeds/178879468 — el vector del breach
El número que “vulneró” el sistema. Vale la pena buscar si ese ID corresponde a algún feed RSS de Reddit, WordPress, o si tiene un significado en coordenadas NMS.
Expect more incoming folks. The Game Detectives Discord has a new post linking to here (#general-discussion), though the poster assumes that it’s a troll vs. an ARG.
That number is actually the WP feed ID for the website that was used to find the tags in the original post, and so most likely a reference to how we used that as the vector to “break in” to the system.
La explicación de Oskar es sólida y probablemente sea la intención principal — 178879468 es el feed ID de WordPress, y que el Architect lo registre como el vector del breach es básicamente un guiño reconociendo exactamente cómo entramos. Eso ya es un detalle interesante por sí solo.
Pero creo que vale la pena no descartar tan rápido la observación de ThatBomberBoi, porque este ARG tiene un patrón muy consistente de significados en capas. Los comentarios en leet speak en el CSS no tienen ninguna función técnica. El contador de partículas en la home está vinculado al día del mes. Los porcentajes de los módulos en el full log no suman 100. Nada aquí parece accidental.
Entonces sí, 178879468 = el feed ID. Y añadiendo un 0 obtenemos lunes 7 de septiembre de 2026 a las 15:24:40 UTC — las 16:24 hora local en UK, primera semana laboral completa después del Bank Holiday de agosto. Hello Games tiene sede en Guildford y Cambridge. Es una ventana muy plausible para que ocurra algo.
Además, el propio sitio tiene Europe/London hardcodeado como timezone en el HTML. El Architect opera en hora UK.
Ambas lecturas pueden coexistir. El feed ID explica cómo llegó ese número ahí. La fecha podría explicar por qué se eligió ese número específico. Si el ARG tiene un punto de llegada, el 7 de septiembre ya está en mi radar junto con lo que sea que traiga el 28 de mayo.
Solo algo a tener en cuenta mientras las cosas se desarrollan
We know that the poem excerpt from the 2005 post so far was just a hint towards the socials, and isn’t actually from Sunday Morning by Wallace Stevens. So, I’ve been curious why the architect would even bother citing that poem. I decided to go ahead and read the real Sunday Morning and here are some lines I highlighted:
"She dreams a little, and she feels the dark
Encroachment of that old catastrophe…"
"Why should she give her bounty to the dead?
What is divinity if it can come
Only in silent shadows and in dreams?"
"She says, 'I am content when wakened birds,
Before they fly, test the reality
Of misty fields, by their sweet questionings…'"
The moral of the poem is the classic “summer is only beautiful when you know winter will come” (pulled that line straight from Season 5 of The Boys lol).
Also might be worth pointing out that one of the first clues from Phase 1 of WT (This is Waking Titan voicemails) was a poem excerpt from Hyperion by John Keats, where the missing word “Hyperion” was our password to login to wakingtitan .com.
I have analyzed the image from the post on May 14th. Here my findings, I can’t find anything on the sound, but the spectrogram shows a pattern, maybe transforming it to numbers instead of sound could lead somewhere @ProjeProje
Hey there, a couple of us are talking in NMScord trying to figure out the precise events that led us to the inside of the Project-Skyscraper.com website (/origin).
I’m curious if you can shed some light on how you found this subdirectory. Did you do a Google search or was it another clue you found which led there?
I believe @DevilinPixy found it using a google search of the site but not 100%, I also stayed up stupid late and it’s 6am now so my brain not work so good; not sure if I’m correctly understanding the query but I think this is what you meant
I believe the page found through this method was the /2026 page
The sitemap doesn’t seem to have every page we’ve discovered but it does seem to serve a purpose of being the pages it wants us to find by such methods. That’s my best guess on the sitemap being so accessible anyway.
Thanks, friend! That answers my query indeed. Rest your brain!
I figure with these types of things, the puppetmasters can always hide whatever they want to. So most of what we easily find can be assumed intentional.
Many people possibly know this already, but we were discussing the networking information on NMSCord and thought I would share the basics for those unfamiliar with standard networking.
The first full security log talks about a WoL (Wake on LAN) attempt on port 9. LAN is Local Area Network, devices separate from the full internet, like all your home devices that are connected to your wireless router. They all get address from the router, usually in the address range of 192.168.x.1-254. Wake on LAN is for when a device is asleep and you want to tell it to wake up, you send 16 packets (called magic packets) on a specified port (usually 9), which it watches for while sleeping. When it gets those, it turns on.
The source address was 192.168.1.100. Typically, you would save addresses ending in .1, .100, and .254 for special devices like routers or servers, mainly just because they are easy to remember. The destination address was 192.168.1.255, which is not usually a normal device address; it’s used to broadcast to the entire network. So device .100 is probably a server that was trying to wake up every device on the network, and the internal firewall blocked it. I guess .100 could be a router and someone hacked into the router from outside and then sent the packets from the internal port of the router, as well.
Anyway, that’s all just some basic explainers to understand that message.
Going off the references to the system’s LAN and @YourBasicMaths’ observations:
I tried sending POST requests with vague connection themed payloads in the JSON body while interpreting the site as a public IP for some part of the Skyscraper System. Its likely not entirely intended, but the puppetmaster should be able to see the requests.
I noted early on that the 3rd line of the verse hadn’t really been applied to the various events so far and realised that it read a bit like an old riddle… No Wing, No Shadow, No trace in the light. ,
What am I?
To which the answer was the Wind.
So the latest security log contains a reference to a memory bloc, and again that translates to a timestamp ; Friday, May 22, 2026, at 00:32:00 UTC.
The question is why 00:32:00 in particular. I don’t remember any logs in-game that referenced that time directly, although there were pieces that did reference how long Atlas had before it became irrecoverable.
@ThatBomberBoi I also did that with an added eventlistener… It returned mostly useless information. There were some things that could be relevant, like the “eventPhase” parameter…
— mencionada en dos logs separados (10 y 12 de mayo) como “Full log”. El número 094127 = 09:41:27, probablemente la hora de un evento anterior a todos los logs visibles. Esta página puede contener el núcleo de la narrativa.
