This is not a drill. This is not a fake. If there’s a better way to prove it, let me know.
I have received guidance from The_Architect.
It appears “waiting” is not the solution, and we are indeed meant to continue digging. Poem page (unstable memory bloc) is the path we need to continue pursuing.
Our MAIN task right now is to identify the corrupted_fragment.
Once we identify the corrupted fragment, it’s important we get this next part right. We need to inject additional data. This means either the corrupted fragment itself, OR valid data that “fixes” the corrupted fragment. I tend to lean towards the ladder, but this is not up to me.
@ThatBomberBoi used a POST method to inject data into Project Skyscraper and this does indeed appear to be a correct action. The data, however, was not valid. And by injecting further unvalidated data, we risk destabilizing the system.
We will find it. We can do this. It’s a nudge, a hint. Because I’m sure they’ve noticed us slowing down a bit.
Here is the message I received from The_Architect:
Network status: nominal
Diagnostic: unstable_memory_bloc= keyPriority task: identify corrupted_fragment
Action required: inject_additional_dataWarning: Injection of unvalidated data may significantly increase system instability
