Vol. II — Method

About the Lab

Broken Branch is the practice of one operator and a fleet of agents, run in public. Here is the why underneath it — and the one thing no afternoon of fixes could ever manufacture.

The lab is named for a broken branch — the one you can finally read, because the break exposes the rings. That is not decoration. The first science I ever did was dendrochronology: reading a tree's whole life out of a cross-section, ring by ring, the drought years narrow and the good years wide, all of it legible in the grain. This whole place is that habit, pointed at new material. A git repository read as tree rings. A core crossdated against a master chronology. A ten-month job search counted out loud, drought years included. One metaphor, carried the whole way down.

What this is

Broken Branch is a one-human, agent-augmented systems lab. Microsoft is the day job, where the work is to master tasks. This is the parallel track, where the work is to master the system. Both are real. This is where the curiosity goes — and where the proof gets made.

The thesis

An operator who masters the system, not the task — and binds himself, fully, to the real mission in front of him. Building in the open, sharing the work. So whatever your problem is, I'm already capable of it — and I'll find the meaning in it with you.

The load-bearing word is system. A task-master has one deep column and breaks when the column changes. A system-master has range because the system doesn't care what domain you point it at. The spread across this lab — physics sims, MCP servers, mobile apps, enterprise Copilot, research tooling — isn't a scattered résumé. It's the fingerprint of system-mastery. Not a generalist. A systematist.

The operator

There's no manufactured mission here. The honest one is a verb, not a noun: explore, create, make art, move the needle — and find the meaning where I go. Meaning isn't pre-declared; it's generated on arrival. That's the explorer's half. It pairs with the rarer one: bind, fully, to the real mission in front of you. Explorers usually don't ship; committers usually don't explore. This lab tries to do both, and keeps the receipts for the shipping. So it isn't a crusade looking for a banner. It's an operator who walks into your mission, makes it survive production, and finds the meaning in it alongside you.

The method — the system being mastered

The lab is a machine for turning curiosity into shipped, surviving artifacts at a sustainable rate. Its organs:

One operator and a fleet of agents. Claude, and the others. Directed, not hand-typed. I decide; the fleet executes; tests verify; the human stays accountable. The operating model is the frontier skill — and the lab's least-copyable asset.

A metabolism. Intake → build → ship → harvest → prune → recurse. Carried on a cadence one body can actually hold: day job, evening peak, an overnight agent batch, a morning review.

Governance as a first-class organ. Permission brakes, a secrets denylist, a legible security surface. Circuit breakers on the carnival ride. The reach stays wide because the brakes are real.

Proof discipline. Every claim sorted by evidence grade. Receipts over vibes: the live link, the source link, the test that caught the bug, the metric — and what failed. When a research run reports its own headline thesis as null, that's not a footnote to bury. That's the product working.

Tests as the trust boundary. Nothing is "done" until it's green and smoke-tested. Verification catches what confidence misses — every time.

The membrane

Some things are public on purpose: the shipped artifacts, the method, the writing, and the honest rings — including the drought years, counted out loud, so the next person can. Some things stay private on purpose: the operator's real location and keys, client-sensitive work, the raw internals of the fleet. The lab shares its method and its results — never its keys. The rule underneath it: unfinished on purpose, but never unclear on purpose. The weirdness is signal; the steel must be findable in five seconds.

The soul

The flagship essay is a cross-section. The first science was reading rings. The newest tool reads a git repo as rings. One image, carried all the way down: a person who reads his own work the way a dendrochronologist reads a tree — ring by ring, drought years and growth spurts legible in the grain. That coherence is the one thing no afternoon of fixes could manufacture. Everything else is fixable bark.

← the journal the lab portfolio in a box github