Architecture
Case studies built to show reasoning, constraints, and the shape of the solution—not just the polished outcome.
ExNulla
I build systems that can survive contact with reality.
ExNulla is where I prove how I think: constraints first, architecture before noise, and delivery that can be inspected instead of merely claimed. This is not a brochure. It is a working proof surface.
Why this exists
I did not come into software through a normal lane. I came in the same way I built businesses: define the problem, map the constraints, design the system, ship the work, and improve what breaks.
ExNulla is the public version of that operating model. The site, the case studies, the demos, the stream, and the surrounding funnel all serve one purpose: make the work visible enough that nobody has to guess what I can do.
What you will find here
- Projects: architecture decisions, trade-offs, and delivery discipline.
- CV: the operator behind the system, framed through execution rather than claims.
- Lab: runnable proof where the ideas stop being theory.
- Meta: build/version provenance and the operating discipline behind the site.
Three ways to read ExNulla
Featured case
Attest Pipeline
Deterministic identity attestation for hostile JSON ingestion, canonicalization, hashing, and cross-institution matching—without turning KYC into a long-term PII honeypot.
This is the kind of work I want to be known for: architecture that closes real abuse paths while reducing operational and data-risk surface area.
Built in public, from zero
The ExNulla ecosystem did not come from an existing employer, audience, or software career path. It was built from zero as a working system: brand, repos, site, demos, stream, and market-facing proof.
- Architecture, implementation, and delivery in the open.
- Public signal designed to compound: site, stream, social, and repos feeding each other.
- Proof-of-work first, credential story second.
Operating stance
- Start with limits, not features.
- Prefer systems that are inspectable, testable, and cheap to recover.
- Use AI aggressively, but keep judgment and accountability human.
- Move fast where ambiguity is low; slow down where the architecture matters.
I am not trying to look like a conventional candidate. I am trying to be legible to the people who know what good systems work looks like.
James Huson
Developer architecture, systems thinking, and public proof-of-work.