>internalkernel Work with me
← build-log

Client zero: the forward-deployed playbook, run on my own desk

· #build-log#agents#workflows

There’s a job title moving through the industry right now: Forward Deployed Engineer. Palantir coined it years ago; the big AI labs hire for it now, and the agent community has adopted it as shorthand for a whole style of work. My day job is this exact motion, embedded inside an enterprise team — which is why the title just earned a row on this site’s services ledger, and why this entry exists.

Buzzwords age badly on a build-log. So before the acronym cools, here is what the title actually names, and the receipt for why this desk gets to use it.

The title, translated

Strip the mystique and an FDE does three things. They embed — inside the client’s team, not behind a ticket queue. They observe — find the workflows that actually eat the team’s week, which are rarely the ones anyone complains about in meetings. Then they systematize — turn those workflows into software the team runs after the engineer walks away.

That last clause is the whole discipline. An automation nobody operates after you leave is a demo. The FDE’s deliverable is a working system plus a team that runs it — which is why the motion resists being productized, and why the labs pay embedded engineers instead of shipping a wizard.

The example: this website’s production line

The cleanest run of the playbook so far is the pipeline that produced the page you’re reading. Two workflows on this desk used to be ad-hoc sessions — writing and design. Both went through the embed-observe-systematize loop this summer, and the second now consumes the output of the first.

Writing went first. The observe step mattered most: the desk’s voice profile wasn’t invented, it was extracted — measured from the ten pieces already live on this log. Reading band, dash policy, the house conventions (callouts as the highlight layer, the honest close, the bookend callback) — all recorded from evidence, the way you’d profile a client team’s real process instead of asking them to describe an idealized one. The workflow that came out of it runs draft → humanize → a lint gate that blocks unverifiable claims → a cold read. The gate is blocking on purpose: prose that can’t survive it doesn’t ship.

Design went second, and it eats the writing system’s output. The design workflow starts with a brief in writing, forces palette and type decisions away from the defaults every model reaches for, and puts generated imagery inside a written honesty boundary — atmosphere and motif are allowed; fake offices, fake teams, and fake screenshots are not. Then it verifies the rendered page, not the intention: contrast sampled from actual pixels, screenshots that scroll so reveal animations can’t hide, a scanner whose findings are treated as a checklist rather than a verdict. Every visible string on the page is written under the voice profile from the writing system. One workflow’s artifact is the other workflow’s input — that’s what turns two tools into a production line.

The receipt is the page

This site’s redesign shipped through that line this week. The brief was written down before a single token of CSS. The night imagery came from the generation rung of the sourcing ladder, inside the boundary, and is disclosed as such in the design record. The scanner that once scored this site’s old source a 43 — “strong AI-default look” — scored the new build a 4. Contrast was measured at 146 sampled positions of the rendered pages: zero failures.

And the proof lives where you can see it: scroll the homepage to 01

and the morning digest prints this repository’s actual latest commits — including the commit that shipped the redesign itself. The production line publishing its own paper trail is not a flourish. It is what a systematized workflow looks like when it has nothing to hide.

What made it forward-deployed, not just automated

Three properties separate this from “I automated some stuff,” and they are the same three I’d hold a client engagement to:

  • Observed first. The voice was measured from live work; the design gates encode failures from real builds. Systems imposed from a template get abandoned; systems extracted from practice get used.
  • Operated after handoff. The human reviews at the gates and the desk runs the rest on schedule — the nightly review reads the exhaust whether or not anyone is typing. A system that needs its builder hovering isn’t done.
  • Auditable by the next run. Every shipped design leaves a fingerprint the next design must differ from; every claim in the copy has to survive the gate again next time. The system checks its future self, which is the only supervision that scales past one engineer.

The honest close

This is an n-of-one. The desk embedded with the friendliest possible client — itself — and a real team adds everything this run didn’t have: approvals, politics, systems nobody remembers building, people whose week you are rearranging. The motion survives all of that (it’s where the discipline came from), but nothing here proves my version of it does at team scale beyond the enterprise work that pays for this desk’s electricity. And the title itself will cool, the way titles do. The motion is older than the name and will outlast it.