PANTHEON
PANTHEON
the person behind it
The substrate, the residents, the Studio, the generative art, the channels, the audit — I designed every part and directed AI to build it, solo. I don't hand-write code; I design the system and direct the machine. This page is the honest version: how it got made, why that matters if you're hiring, and the hard problems I haven't solved yet. I'd rather you trust what's real than be sold what isn't.
foundations first
Not fastest-first. Foundations-first — and I enforced the foundations on myself.
I built it from packages/pantheon-core outward and made the layering a hard rule: core ⊥ residents ⊥ bundles. A lint and an AST test fail CI with PURITY VIOLATION — core depends on a downstream layer. The substrate physically can't import its own residents. Nobody made me do that on an AI-built system — that discipline is what you'd be buying.
The reasoning loop, the authorization gate, the crisis protocol, overdraft-proof metering — the control plane came before the product. Retrofitting safety is how you ship the incident.
Two unrelated businesses run on one spine, proven by that same purity lint. That's the line between infrastructure and a slide deck.
An 80-agent, 14-facet audit where every finding was refuted before it counted, then fixed and redeployed. I attack my own work harder than a reviewer would.
Anyone can wire a model to a prompt. The hard part — the part almost nobody builds — is everything between a clever demo and a system you can safely put other people's money and data through: isolation, governance, metering, and the honesty to say what it can't do. So I designed that and directed AI to build it, alone, all the way to production. The system refuses. The meter can't overdraft. A person in crisis reaches help even at zero credits. I care about the problem more than the pitch.
— Isaac
the path here
I studied Financial Mathematics at the University of Greenwich in London. The pandemic cut it short. But it left me the part that matters: I can think in abstractions, and I work things out from first principles instead of taking a framework's defaults on faith.
I spent most of the next two years in Argentina, teaching myself the systems that now shape everything I build. Mostly Ethereum. My first real project was flash-loan arbitrage bots — atomic, all-or-nothing transactions in an adversarial mempool. That drilled in two instincts: atomic-or-revert, and assume everyone's an adversary. It's also what got me into Linux and running my own infrastructure. Most of all, it left me one rule: don't trust, verify. A guarantee isn't a promise you make — it's something you build into the system so nobody can talk it away.
That rule is the spine of PANTHEON. Tenant isolation isn't trusted to app code — the database enforces it on a role that can't bypass it. An agent can't approve its own consequential actions — the permission is revoked, not discouraged. The meter can't overdraft or double-charge. Every safety property is verified by the layer below, never trusted to the layer above. I didn't set out to rebuild Ethereum's mindset around AI agents — but that's what PANTHEON turned out to be.
still unsolved
I'd rather tell you this now than have you find out later — every claim on this site comes with its own asterisk.
One production instance, by choice. Horizontal and multi-region scale is designed for but unproven — I haven't run it at that scale yet, and I'll say so before you ask.
Mitigated by defence-in-depth — scoping, the audit judge, human approval gates — not solved. Nobody has solved it; I won't pretend otherwise.
Adversarially tested, and it held. But adversarial testing is strong evidence, not a formal proof. I know the difference and I won't blur it.
The §14 quality gate certifies bundles; the live Studio ship-path is gated by the deterministic generator's own invariants plus a readiness check. I keep the docs honest about which gate does what.
let's talk
Someone who designs the system, directs the build, attacks his own work, and tells you what isn't done. Here's the role I'm after — and I'm open to relocating anywhere in the world.