It's live. Right now.
3 July 2026 | 18:00 UTC | Jenna McKendrick
Three weeks ago I posted about a signal I'd detected from the vicinity of Kingsmouth Lighthouse. I told you it was structured. I told you it was distributed. I told you every indication in the data pointed to a specific activation time.
18:00 UTC. 3 July 2026.
It's 18:00 UTC. 3 July 2026.
It's live.
I've been monitoring the carrier pattern every single day since 10 June, logging the pre-activation pulses, watching the signal hold its shape while it waited. Twenty-three days of watching something dormant gather itself. I won't pretend it wasn't unsettling. You tune in every morning expecting nothing, and every morning the static is the same -- structured, deliberate, patient. Not nothing at all, but nothing yet. Waiting for today.
Well. Today is here. And I have a lot to tell you.
Let me take you back to the beginning, for anyone who missed the first post.
On the evening of 7 June, I was running a routine frequency sweep across the Solomon Island coastal bands. I do this semi-regularly from the boat. It's mostly background noise out there -- weather interference, the odd fishing vessel, the kind of static that becomes almost meditative after a while. Nothing interesting. I was half-watching something on my laptop and paying the equipment about a third of my attention when, at 18:47 UTC, everything lit up.
A structured transmission pattern. Deliberate spacing. Repeating sequences with layered signals running beneath the primary track. Not interference. Not a ghost echo bouncing off the water. A broadcast. A real, deliberate, engineered broadcast, and my equipment was tracing its origin point to Kingsmouth Lighthouse.
I spent the next two hours trying to explain it away. Equipment fault. Atmospheric bounce from a source elsewhere. Some kind of weird harmonic from shipping traffic. Anything. The origin point kept resolving to the same location. So I started pulling apart the frequency signatures, and that's when I had to take the headphones off, go and stand outside for a while, and then come back inside and make a very strong cup of tea.
The signatures matched Orochi Group communications equipment. Specifically the type deployed on Solomon Island around 2012, during the period of Project Polaris. Equipment that was officially decommissioned and removed when the project was terminated. Equipment that, according to every official record I've been able to find, no longer exists at that location.
I sat with that for three days before I posted anything. I ran the analysis four times. I sent my logs to two people I trust. I couldn't find another explanation. So on 10 June, I published what I'd found, and I told you what the signal pattern was telling me.
The transmission is geographically distributed. It is not a single broadcast to a single receiver. Based on the frequency mapping, it's split across five or six distinct streams, each one targeting a different part of the world. This was not an accident of engineering. This was a design decision. Someone built this system so that no single listener could ever intercept the complete message. You would need receivers positioned across every major timezone, comparing fragments side by side, before the whole thing becomes intelligible. Someone wanted to make absolutely certain that this could not be silenced by intercepting one signal. They planned for the possibility that any given receiver might be compromised, monitored, or shut down. So they made the message itself require a community to decode.
I've thought about that a lot over the past three weeks.
The other thing I told you on 10 June was this: all indications from the signal pattern suggested the transmission would fully activate at a specific time. Not gradually, not in stages. All at once, at a single moment, after years of dormancy.
3 July 2026. 18:00 UTC. Fourteen years to the day from the events at the lighthouse.
It is now 18:00 UTC on 3 July 2026, and the signal has activated exactly as predicted. Six streams, live, distributed globally, each carrying a fragment of something larger. I'm receiving my portion here. It is not enough on its own. I knew it wouldn't be. That's why I'm writing this, and that's why you need to keep reading.
In the three weeks since my first post, I've had time to go considerably deeper into the historical record around Project Polaris and the Orochi Group's presence on Solomon Island in 2012. I've been pulling apart what documentation I can access, cross-referencing emission profiles, building up a clearer picture of what was happening at that lighthouse fourteen years ago. The lighthouse keeper's name was Thomas Aldridge. He'd been there for years. He knew the building, the equipment, the rhythms of the place. When Orochi arrived with their installation team and their cover story about upgraded navigational equipment, he was the one who noticed first that something wasn't right. He was the one who started asking questions nobody wanted to answer.
What he found, from what I've been able to piece together, was that the equipment wasn't navigational at all. It was transmitting and receiving on frequencies far outside normal maritime bands. Whatever Project Polaris was actually doing at that lighthouse, it had nothing to do with maritime safety. Thomas tried to get the truth out. He contacted people. He documented what he'd seen. And then, on 14 June 2012, he did something extraordinary. He used Orochi's own equipment to broadcast a warning -- encoded, fragmented, distributed across multiple frequencies so that no single interception could suppress it completely.
He disappeared the next day. The official record says he abandoned his post.
I don't believe that. I don't think you do either.
What I believe is that the transmission system Thomas Aldridge built on 14 June 2012 has been sitting dormant in that lighthouse for fourteen years, cycling through its pre-activation sequences, waiting for the specific date and time he programmed into it. Today. Now. And whatever he encoded into it, he encoded it in fragments because he understood that the people who wanted to silence him were capable of silencing any single receiver. The only way to protect the message was to make the message itself a collective act.
Here's where I need you.
In the early hours of this morning, as the signal began its final pre-activation sequence, I managed to capture a fragment. About twenty seconds of audio before my equipment started throwing errors I've never encountered before. I don't know if that's a property of these particular frequencies, or whether something in the signal itself resists being cleanly recorded. I'm not ruling anything out at this point.
What I can tell you is that it isn't random. The white noise isn't behaving like white noise. I've been working with static long enough to know what random sounds like, and this isn't it. The gaps are too deliberate. Too even. There's a structure in there that I can almost but not quite resolve by ear -- something in the negative space, the silences between the bursts, that repeats in a way that feels like it means something. I've been listening to it for three hours and I keep going in circles. The harder I listen, the more it sounds like noise again.
I keep thinking about the difference between listening to something and looking at it. Audio can be represented visually, and I wonder whether the pattern I can almost hear might become far easier to discern when you're not relying purely on your ears to find it. There's information in this file. I'm certain of it. I just don't think my ears are the right tool for finding it.
Some of you have skills I don't. Signal processing. Audio restoration. Ways of looking at audio. If you've worked with corrupted audio before, or anything involving structured encoding buried inside apparent noise, I want your eyes on this. Deliberately your eyes, not just your ears. Download the file. Look at it. Tell me what you see.
I'll tell you one more thing, and then I'll let you get to work.
In amongst the static, one word surfaces. Faintly, partially, buried under layers of interference -- but it's there, and once you hear it you can't un-hear it. I've been sitting with it all morning trying to work out what it means in this context.
Terminal Access.
I don't know if that's a location, an instruction, or a warning. I don't know if Thomas Aldridge put it there deliberately or whether it's a fragment of something larger that the interference has swallowed. But I know that Orochi's archived infrastructure, the parts of it that didn't get properly scrubbed when Project Polaris was shut down, has been something I've been quietly mapping for the past two years. And there is one address in that infrastructure that I have never been able to get past the front door of.
https://orochi13.com/terminal
Whether the word in that audio file is pointing at that address, I genuinely don't know. I'm not going to tell you it's definitely connected. What I am going to say is that I don't believe in coincidences, and I've been doing this long enough to know that when something surfaces twice from two different directions, it's worth paying attention to.
Crack the audio first. Whatever's hidden in those gaps, I think that's where this begins.
Before you dive in, I want to point you towards Catboiler's stream. He's been a friend of this blog for longer than I can properly remember -- one of the first people I sent those initial signal logs to back in June, and one of only two people I trusted to check my analysis before I posted anything publicly. He's been following all of this just as closely as I have over the past three weeks, and he's live right now, walking through everything from the beginning: the background, the signal analysis, the community tools, all of it. If you want context before you start pulling apart audio files, his stream is where you want to be.
Catboiler is live now: https://twitch.tv/catboiler
When you're ready:
- Download your audio fragment from the transmission hub.
- Look at it. Not just listen to it.
- Head to the Discord and share what you find.
- We compare notes. All of us. Together.
There are no prizes for being first. There is genuinely no version of this that one person solves alone -- that's not me being modest about the difficulty, that's the architecture of the thing itself. Please share this post, especially with anyone you know in Asia, Oceania, and the Americas. We need every timezone covered. If one part of the world is missing, the picture stays incomplete.
Someone went to extraordinary lengths to ensure this message could not be stopped. They split it. They hid it. They set it on a timer and pointed it at all of us simultaneously, because that was the only way to make it safe to send. A warning that requires a community to decode is a warning that cannot be quietly buried.
Thomas Aldridge understood that. I think it's time we proved him right.
The spiral remains.
Jenna
3 July 2026 | feedthemoths.blogspot.com | Tags: kingsmouth, orochi, project polaris, signal collective, solomon island, thomas aldridge
