There are three things I’m working on. I want to explain why that number is not a coincidence, why the order is not arbitrary, and why the three together say something that none of them can say alone.
This is not a portfolio. A portfolio is a collection. What I have is a trajectory — and the distinction is everything.
The Question Behind Every Project
When someone asks what I’m building, I could list the projects. I could describe the domains, the tech stacks, the market opportunities. That answer is accurate and completely useless. It tells you what without touching why, and it says nothing at all about how I choose.
The real answer lives in three verbs: secure, build, anchor.
Each one is a layer. Each layer enables the next. And together they describe a method for deciding what’s worth doing — not a menu of things I happened to get interested in.
Layer One: SECURE
The foundation is Darkwave.
Twenty years in security is a long time, long enough to understand something that most people building products prefer not to think about: you cannot create durable value on unsafe ground. It doesn’t matter how elegant the product is. It doesn’t matter how sharp the UX is or how clever the business model. If the substrate is compromised, everything built on top of it is borrowed time.
Security work taught me to think in threat models before I think in features. It trained me to ask not what can this do but what can go wrong with this, and when, and for whom, and at what cost. That is a genuinely different cognitive posture from most of what passes for product thinking.
Darkwave is where that posture lives professionally. It’s where the discipline is kept sharp. And it’s why I can approach any subsequent layer with clear eyes about what “safe to build on” actually means — not as a checkbox, but as a real and specific standard.
SECURE is not preliminary work. It’s not the stage you rush through to get to the interesting stuff. It is the interesting stuff. It just doesn’t always look like it from the outside.
Layer Two: BUILD
Once you know how to secure something, you can see the broken things clearly.
Most friction in the world isn’t mysterious. It’s the gap between how something should work and how it actually works — and that gap is usually visible to anyone paying close enough attention, long enough. The people who live with the friction stop seeing it. They adapt around it. They call it normal.
I don’t think normal is a good enough answer.
Shaka is where I apply the security mindset to actual product friction. Not abstract friction — real, specific, felt friction in a domain I care about. The move from SECURE to BUILD isn’t a pivot or a distraction. It’s an application. The same discipline that says identify what’s actually failing, not what’s visibly failing applies directly to understanding why real people hit the same wall in the same place every time.
Building here means two things at once: building the product that removes the friction, and building the credibility that comes from having actually solved a real problem for real people. The second is harder and slower than the first, and it’s the only one that matters past year one.
SECURE gives you the standards. BUILD puts them to work in the world.
Layer Three: ANCHOR
Securing things and building things are both temporary acts if there’s nothing holding them in place.
This is what Queensland is about. Not in a geographic sense — the name is a marker for something more structural: the idea that some infrastructure needs to become permanent and sovereign, or it doesn’t really exist. It can be taken away. It can be de-platformed, deprecated, acquired, or simply switched off by a party whose interests no longer align with yours.
ANCHOR is the layer where I ask the hardest version of the question: what would have to be true for this to still exist and still work in twenty years?
That question immediately filters out a lot. It filters out anything whose continued existence depends entirely on a third-party platform’s goodwill. It filters out anything that hasn’t thought about governance. It filters out anything that optimises for today’s distribution channel at the expense of tomorrow’s independence.
Making infrastructure permanent and sovereign isn’t a political statement. It’s an engineering one. It means the thing can’t be easily dismantled by forces outside the system. It means ownership is clear, control is real, and the people who depend on it aren’t one API change away from losing everything they built on top of it.
SECURE lays the ground. BUILD raises the structure. ANCHOR makes it stay.
How Each Layer Enables the Next
This is the part that matters most.
If I didn’t have twenty years of security discipline, I would build things with hidden fragility. I would optimise for speed and elegance and user delight and ship something that looks good and works badly under pressure. SECURE is what makes BUILD honest.
If I didn’t build real things for real people — things that had to work, had to survive contact with users, had to earn their place — I would have no basis for knowing what’s worth anchoring. Not every structure deserves permanence. ANCHOR is expensive and slow, and applying it to the wrong thing is worse than not applying it at all. BUILD is what gives me signal about what’s actually worth locking in.
And if I didn’t have the ANCHOR layer in view, I would build things that are chronically dependent — on platforms, on investors, on the goodwill of parties whose priorities will eventually diverge from mine. Having ANCHOR as a destination changes the design decisions I make in the BUILD layer. It changes what I’m willing to accept as a dependency. It changes how I think about ownership from the very first line of code.
The three layers don’t just coexist. They instruct each other.
Trajectory Over Portfolio
Here’s what I’ve noticed about people who present portfolios: the implicit message is look at the range of things I can do. Versatility is the point. The breadth is the proof.
I’m not interested in proving breadth.
What I’m interested in is coherence — and coherence only emerges over time, from a series of decisions that follow the same logic. Trajectory is the evidence of that logic playing out. A portfolio is what you show when you want to impress someone quickly. A trajectory is what you have when you’ve been thinking seriously about the same underlying problem for a long time.
The underlying problem I’ve been thinking about for a long time is this: how do you build things that are genuinely trustworthy and genuinely durable? Not trustworthy in a marketing sense. Not durable in a “we hope the market stays the same” sense. Actually, structurally, demonstrably trustworthy and durable.
SECURE, BUILD, ANCHOR is my answer. It’s not a complete answer. But it’s a real one, and it’s mine, and every project I take seriously has to fit somewhere inside it.
How I Pick What to Work On
The three-layer test is actually a filter.
When something comes across my attention — an opportunity, a problem, a domain, a collaboration — I ask where it lands. Is this a SECURE problem? Is this a BUILD problem? Is this an ANCHOR problem? If I can’t place it, I don’t take it on. If it sits comfortably in one of the three, I want to understand what it gives to the layers above and below it, and what it needs from them.
Projects that don’t connect to the progression aren’t bad projects. They might be genuinely interesting, commercially attractive, technically stimulating. But they’re not my projects. Someone else should build them — someone for whom they’re load-bearing, not decorative.
This is what “no selling” actually means in practice. I don’t need to attract every potential collaborator or client. I need to attract the ones who are working on the same class of problem, and for whom SECURE → BUILD → ANCHOR is legible as a serious framework rather than a catchy tagline. Those are the people worth working with. Everyone else will find someone better suited.
Where It Goes Next
The honest answer is that I don’t know the full shape of what comes after Queensland.
What I do know is that the method generalises. SECURE → BUILD → ANCHOR isn’t specific to cybersecurity, or to surf culture, or to regional infrastructure. It’s a logic for approaching any domain where something valuable is being eroded by insecurity, friction, or impermanence.
There are a lot of those domains. Most of them are not being addressed by people who think this way. The default approach is to build fast on whatever platform is popular, optimise for acquisition metrics, and exit before the fragility becomes visible. That approach produces a lot of exits and a lot of wreckage.
I’m not interested in the exit. I’m interested in the thing that’s still standing.
The cornerstone is laid. The method is clear. What gets built on top of it has to earn its place — layer by layer, in order, with intention.
That’s the whole manifesto.