The Stella Behind
Punk Records
I'm a Product Manager with experience across startups from seed to IPO, specializing in risk and business integrity. For years, I did what PMs do — wrote specs, ran ceremonies, argued about priorities in rooms where everyone nodded but nobody aligned.
Then AI agents got good. Really good. And I realized the job description I'd been following was about to become obsolete — not because PMs don't matter, but because the translation layer part of the job no longer does.
The Shift
Instead of writing a document and handing it to engineers, I started writing the logic so precisely that an AI agent could execute it. Instead of managing a team's velocity, I started directing a squad of AI satellites — each one specialized, each one tireless, none of them needing a standup.
The results were startling. Projects that would have taken a team of four engineers two sprints were shipping in days. Not because the AI is magic, but because the architecture was airtight. When the blueprint is precise, execution becomes mechanical.
Stella & Satellite Methodology
The name comes from One Piece's Vegapunk — the world's greatest scientist who stored all his knowledge in Punk Records and split his consciousness across six autonomous Satellites, each handling a different function. The original body, the Stella, serves as the core logic engine.
That's exactly how I work now:
I think. I architect the system. I map the risks. I write the blueprint so airtight that any satellite can execute it.
Claude, Cursor, specialized agents — they build, test, and deploy. They handle the execution in their domains of expertise.
This site. The open-source brain. Every blueprint, every build, every failure — documented.
What You'll Find Here
This is not a portfolio. It's a lab notebook. You'll find the raw .md files
behind every build. The exact prompt chains that worked. The ones that didn't.
The risk matrices. The moments when Claude hallucinated an entire auth flow
and the whole build had to be restructured.
Every project ships publicly. Every decision is documented. No corporate polish. No "thought leadership." Just the work.
Currently Building
I'm shipping one project per week, documenting the entire process. The deployments range from practical tools to personal projects — each one testing a different aspect of the Stella & Satellite methodology.
Follow the Satellite Logs for the full build stories, or check the Deployments page to see what's live.
The Stella doesn't code. The Stella thinks.
— v1.0, The Stella Protocol