Systems explained by
how they work.

Project / 01

TechBearing — Operator OS

Problem boundary

Operational knowledge was scattered across infrastructure, repositories, telemetry, notes, and runbooks—and repeatedly lost between sessions. Operators and agents needed one durable, queryable view of what changed, what mattered, and what happened next.

Project / 02

Bricktelligence — The AFOL Companion

Problem boundary

Serious collectors live across a stack of databases — Brickset, BrickLink, Rebrickable, Brickeconomy. They are catalogs: look something up, leave. None of them know your collection, your build habits, or whether the set you are eyeing is actually worth it for you. The hobby was drowning in reference tools and had no companion.

Project / 03

The Hive — Homelab Platform

Problem boundary

Cloud-native systems only become intuitive when you live with their failure modes. The goal was to build a durable environment where networking, storage, delivery, identity, observability, and application operations could be learned as one connected system.

Project / 04

The Archivist Stack — Open-Source AI Substrate

Problem boundary

Three unrelated products kept converging on the same architectural shape. Rebuilding that substrate from muscle memory was useful evidence, but wasted motion. The reusable machinery needed to become inspectable, adoptable, and safe to build on.