operator 8 public repos

the operator's board

Christopher Youngblut

It's all mechanisms and systems. I read a system by how it works, not what it's called, and build the tool it's missing — then run it. Everything on this page is served from hardware I own, through a stack I built, behind gates I review.

8
project umbrellas
8
public repos
10
writeups
1
operator

Build the system once, instantiate per domain.

The provenance is real: a farm, a law office, trust & safety at scale, a self-run rack — and ten years as my own mechanic. Different territory, one discipline: find the deviation before the failure, treat documentation as a control system, formalize judgment so it survives volume. Extract the mechanism cleanly and it transfers. The stations below are the same operator, instantiated six ways.

Ag + edge

The edge unit only listens. The protocol library is public.

open station ▸close ▾

Sprayer retrofit on the family farm; an open CAN/ISOBUS protocol library; an RTK edge unit that rides along.

industrial edge

Legal AI

First version shipped in seven days, for a real case.

open station ▸close ▾

Privilege-aware retrieval in production with a small practice — document access enforced in code, not policy.

architecture

The fleet

This page came off that rack.

open station ▸close ▾

Multi-GPU serving behind a hand-written router; local inference tuned to its silicon; a self-run tailnet.

inference work

Platform

One engine, many packs. This page wears the same system my internal consoles wear.

open station ▸close ▾

Spaces freezes and thaws whole workspaces; an eval harness takes domains as data packs; a design system as the token contract.

platform layer

Taxonomy

The question is never “what have I done” — it's what survives the domain change.

open station ▸close ▾

The recurring mechanisms of my own career, extracted, made queryable, and tested against what the market asks for.

the writing

Co-authoring

Introduced properly, not footnoted.

open station ▸close ▾

Most of this work has a partner. The method — and the boundaries — are documented.

meet the co-author

The gates.

Everything public passed through gates — mapped, built, adversarially reviewed, then released. The keystroke that puts a thing in production is mine. Nothing here is cemented; constant refinement is the practice. The projects are the capabilities; the writing is the proof.