ExNulla Site: static-first proof-of-work portfolio
Astro + Nginx portfolio system with atomic releases, isolated demo artifacts, provenance-aware builds, and operational guardrails designed to survive real updates.
astronginxatomic-releasescicd
CV
Digital CV
ExNulla is my public proof-of-work: architecture, build, deploy, operations, and market signal in one system. I design for constraints first, ship with discipline, and prefer solutions that can prove value early without demanding heavy capital up front.
Proof of work
Designed, architected, and deployed the entire ExNulla engineering ecosystem — repositories, CI/CD pipelines, infrastructure, demos, documentation system, and live development platform — as a single operator in 23 days using a structured AI-assisted development pipeline.
What I do
- Developer architecture: frame the problem, lock constraints, define boundaries, choose the build path, and document the trade-offs.
- Delivery systems: static-first architecture, TypeScript strict, Node, Astro, Nginx, GitHub, DigitalOcean, Cloudflare, and boring deploy discipline.
- Business architecture: design systems that can start lean, show value quickly, reduce waste, and harden as the opportunity becomes real.
- AI-assisted execution: blueprinting, engineering specs, deterministic build workflows, and turning AI from a novelty into a usable production multiplier.
TypeScriptNode NginxAstro DigitalOceanCloudflare
Operating principles
- Start with the problem, the constraints, and the economics—not the tooling.
- Prefer static-first, composable systems over heavy stacks with unclear operating cost.
- Make deployment boring, rollback cheap, and provenance visible.
- Prototype fast, then harden deliberately when the design proves it deserves to live.
- Use AI aggressively, but keep architecture, judgment, and accountability human.
ExNulla is the reference implementation of how I work: deliberate scope, visible proof, repeatable delivery, and a bias toward systems that survive contact with reality.
Why ExNulla exists
- Background: I spent 20+ years designing and building businesses, operations, and revenue systems long before I ever touched a public tech title.
- Transition: I moved into software architecture by doing what I have always done: define the problem, design the system, build the assets, test the market, and improve the weak points in public.
- ExNulla: the entire ecosystem—brand, repos, site, stream, demos, social funnel, and operating model—was built from zero and pushed into public view in its first 23 days.
- Point of the project: I did not wait for permission to get “experience.” I built the experience, documented it, shipped it, and made the work inspectable.
The result is not a résumé pretending to be technical. It is a technical system that also functions as a résumé.
Range
- Software / infra: TypeScript strict, JavaScript, Node.js, Astro, Vite, Nginx, Git/GitHub, PostgreSQL basics, SQLite, GraphQL exposure, Rust in active learning, Docker-aware CI/provenance thinking.
- Cloud / delivery: DigitalOcean, Cloudflare, Vercel, static deploy architecture, artifact isolation, version stamping, CI/CD hygiene.
- Creative / tooling: Blender, SketchUp, 3D CAD, Premiere Pro, DaVinci Resolve, documentation systems, spreadsheet and financial workflow tooling.
- AI stack: ChatGPT, Grok, Claude, Perplexity, DALL·E, and deterministic multi-agent build workflow design.
What I am optimizing for
- Near-term role: developer architecture with real ownership—someone who can bridge product, operations, business constraints, and implementation.
- Longer path: the lane between dev architecture and executive systems leadership: the kind of work that lives between CIO, COO, CINO, product strategy, and engineering.
- My edge: I do not just think in code or just think in business. I think in systems that must be built, operated, explained, and made economically viable.
I am strongest where architecture, execution, and commercial reality all have to agree.
Case studies (curated)
Stream Ops: deterministic live production stack
OBS, Multi-RTMP, Streamer.bot, browser overlays, generated media, and operator runbooks turned into a repeatable production system instead of a pile of fragile settings.
obsautomationopsrunbooks
Space Server: 50 kW orbital compute trade study
Constraints-first architecture work on orbital AI infrastructure: power budget, GPU packing, radiator physics, launch packaging, and the discipline to separate speculation from locked assumptions.
thermalsystemsarchitecturecompute