I'm your huckleberry.

work in hand

Some of what I'm building.

Circuits, tube amps, pollinators, drone gear — pieces of a toolkit that runs without anyone's permission.

Tucson, Arizona

Saguaro country.

Moving to the desert. Mom and me, starting over where the air is dry and the sunsets don't quit.

through the lens

Quiet places.

iPhone, DJI, patience.

from above

Aerial perspectives.

DJI Mini 4 Pro. The Ozarks and the desert from 400 feet.

say hello

Let's talk.

under the hood

This site is a computer.

Not a metaphor. A Service Worker intercepts every request and runs a microkernel — capability-gated IPC, a virtual filesystem backed by Cache API, an autocatalytic SQLite cache (ZLCE), a full-text search engine, a property graph with holographic vector embeddings, and P2P mesh networking. No server framework. No npm. One static HTML file, one Caddy, and a 12,000-line Service Worker that IS the application server.

Browser
  └── Service Worker (microkernel)
       ├── KernelIPC — typed message passing
       ├── VFS — virtual filesystem (Cache API)
       ├── ZLCE — autocatalytic cache (SQLite WASM)
       │    └── 3799ms → 3ms (1,266x speedup)
       ├── Harbor — FTS5 search engine
       ├── Knowledge Graph — HRR vector embeddings
       ├── PeerMesh — WebRTC P2P networking
       ├── Meadowcap — capability-based access control
       ├── Ed25519 — module integrity attestation
       └── v86 — x86 emulator (boots Linux in 1s)
            └── GNU Hurd (three microkernels deep)

Zero API keys. Zero cost. Runs offline. Your browser, your data, your compute. The same protocol runs on bare metal GNU Hurd via Mach IPC. Every module is a sovereign translator — browser and hardware speak the same language.