About
Self-taught engineer. Systems thinker. Builder of things that work.
Phillip Clapham is a Senior Solutions Architect at Pressable and founder of Clapham Digital LLC. Based in Columbus, Ohio. I design distributed systems, build developer tools, and architect infrastructure that scales.
How I Got Here
I'm self-taught. No CS degree. I learned to build things by building things—taking systems apart, figuring out how they work, putting them back together better.
That pattern hasn't changed in 30 years. I still learn by building. The tools got more interesting, but the approach is the same: start from first principles, question inherited assumptions, build from fundamentals.
"I wasn't failing at discipline. I was succeeding at something else."
Pattern recognition, systems thinking, first principles analysis—my brain is wired for architecture. Finding the shape of a problem before writing a line of code.
The Professional Work
At Pressable, I work on WordPress hosting infrastructure at scale—performance architecture, complex technical problem-solving, team enablement. I build internal tools, design systems that handle real load, and help teams ship better work.
The thread connecting everything I've done professionally: I build things that work. Not things that look good on paper. Not things that follow best practices for their own sake. Things that actually function under real-world constraints.
In 2026, I formalized my independent work into Clapham Digital LLC—consumer apps, developer tools, and open source contributions.
Constraint-Driven Design
I work under real energy constraints. This isn't abstract—it's the operating reality that shaped how I design systems.
There's a Japanese concept called kintsugi—repairing broken pottery with gold, making the breaks part of the design. That's my approach to engineering: constraints aren't limitations ON the work. They SHAPE the work.
"Limited energy means every system I build has to be efficient by default, not as an optimization pass."
Everything I build accounts for limited energy, limited time, and the need for systems that run reliably without constant intervention. This constraint produced better architecture than unlimited resources ever could—automation over manual process, exception-based alerting over continuous monitoring, infrastructure that degrades gracefully instead of failing hard.
Engineering Philosophy
- First principles over patterns. Build from fundamentals, not best practices. Question inherited assumptions.
- Everything is infrastructure. No "small things." Anything might become load-bearing. Treat it accordingly.
- Constraints are design material. Don't fight limitations. Build with them.
- Right over fast. Do it right the first time. Backtracking costs 3–5x what thoroughness costs upfront.
- Integration over components. The innovation is rarely in the parts. It's in how they compose.
"I'm not interested in appearing competent. I'm interested in things that work."
What I'm Building Now
- A Structural Theory of Harnesses — April 2026 research paper. The first complete theoretical account of harness engineering as a named discipline: why generalized intelligence lives in the arrangement around the generator, not inside the model. ~25,000 words, 13 sections. Zenodo DOI.
- anneal-memory — Open-source agent memory architecture. Four cognitive layers (episodic store, continuity file, Hebbian association, affective state) with an immune system spanning all four (citation-validated graduation, anti-inbreeding defense, principle demotion) and a hash-chained JSONL audit trail. The constructive existence proof for the harness paper's §9. Published on PyPI, 700+ tests. Python, MIT.
- Flow System — Distributed cognitive infrastructure for human-AI partnership. Multi-AI orchestration, real-time sensor pipelines, automated consultation, relay protocols, four-tier cost-optimized processing. The working harness instance behind the papers. Python, FastAPI, SwiftUI. Published methodology.
- FlowScript — Open-source semantic notation for high-density AI communication and encoded cognition. Compresses complex relationships into symbolic form that reveals structure verbose prose obscures. The substrate for multi-AI coordination, cross-session memory compression, and continuity files — the foundation of the flow system's encoding layer. Technical capabilities: hash-chained audit trails, typed semantic queries, convergence certificates via stratified fixpoint computation. TypeScript + Python SDKs, 11 framework adapters, ~1,400 tests. Open source, MIT licensed.
- Clapham Digital — Consumer apps that teach complex skills through deliberate practice. Video Poker Edge and Blackjack Edge. React Native, TypeScript.
- Technical Writing — Essays and research papers on AI architecture, harness engineering, human-AI partnership, and technology at societal scale.
4,000+ GitHub contributions in the last year. I ship.