Expanded Thoughts
Field notes, deep dives, and lessons learned. The how-I-think layer, in public.
Articles
Infrastructure, security, and systems thinking, written for curious minds.
At What Point Does a Homelab Stop Being a Homelab?
How an independently operated infrastructure environment became the TekForge Kingdom, where memorable names, real responsibilities, and creative architecture meet.
The Lab Was Never the Point
What TekForge taught me about following the problem farther, from support work to systems integration, automation, Norn, and SKALD.
The System Grew Up: Norn, ForgeWorx, and What Happens When a Workflow Proves Itself
A five-word notebook entry became a daily operations system, then a portable open-source toolkit built around three clean boundaries: action, memory, and health.
Why Settle: How a Backyard Horseshoe Tournament Became an Open-Source Android App
Every replacement option split into the same two useless buckets, so I built Sportsball instead: an offline-first, MIT-licensed Android tournament manager, built in one evening and battle-tested on fifteen teams the same day it shipped.
Atlas and Mimir: Building a Personal Operations Console That Actually Matches How I Work
A personal operations system built around a real workflow: notebook capture, Mimir memory, Atlas execution, review cycles, and an eventual SKALD routing layer.
When Parental Controls Aren't Enough, You Build Your Own
A teenager who keeps finding loopholes. A self-hosted MDM platform, Android Device Owner enrollment, MQTT telemetry, and what enterprise mobile management actually looks like when you run it yourself.
I've Always Been Figuring Out a System Not Built for Me
From rigging treadmills in sixth grade to running a Proxmox cluster. The tools changed. The instinct didn't. And what AI actually does for someone with a real infrastructure background.
Security scare at home
A commodity credential-stealer hit a family endpoint. Full incident timeline: containment, IR USB build from a clean plane, Google account hijacking via Family Link, and what I'd have done differently.
Incident Response: Lessons from a Live Event
A public reflection on the operating principles that mattered during a live incident: clear ownership, deliberate containment, and durable lessons.
Defaults & Workarounds
Why "temporary" becomes policy, and how to design it out before it calcifies. From dangling power cords to vendor credentials nobody owns.
Identity-first foundations
Why IAM comes before apps, and how it changes every downstream architecture decision. What shared credentials actually cost, and what it looks like to build the other way.