Dex Horthy: harness engineering isn't enough, and the comment thread proves it

Horthy's talk write-up hit Hacker News July 23 with 356 points and 254 comments. HumanLayer's founder lays out a three-layer model that's the most useful vocabulary I've picked up this month.

The loop is one agent: gather context, act, check, repeat. The harness wraps it: sandbox, tools, persistent memory, done-gates. The factory wraps that: intent and production signals feeding a queue through build, automated checks, review, deploy, monitoring.

His argument is that people build the factory and expect it to run unattended, and it doesn't. Humans stay in the loop, but not as line-by-line authors. As runtime support. Identifying which context is relevant. Explaining how the repo is actually structured versus how it appears. Selecting tools. Enforcing architectural boundaries the agent has no way to infer. Cleaning up residue.

That list is the honest version of what I do all day. I'm not writing much code. I'm doing context selection and boundary enforcement, and calling it engineering, which it is, but it's a different job than the one I trained for.

The comment thread is the actually valuable artifact. It splits cleanly. One camp is practitioners describing large incoherent agent PRs, code that passes tests and review and is structurally wrong in ways nobody catches for two sprints. The other camp bets that models improve faster than codebases rot, so the incoherence is a temporary tax on early adopters.

I think the skeptics are wrong, and not for capability reasons. Model improvement doesn't fix architectural incoherence because architecture is a choice, not a correctness property. A better model makes locally better choices faster. It doesn't know that your team decided six months ago to keep all payment logic behind one interface, unless something tells it, and that something is either a human or a harness artifact a human wrote.

Which is exactly Horthy's point about done-gates living in the harness layer. The boundary enforcement has to be encoded somewhere durable. If it lives in your head and you communicate it per-PR, you're the bottleneck and you scale linearly.

What I'd do this week: write down the three architectural rules you'd reject a human PR over. Put them in your harness as a check, not a prompt. Prompts are advisory. Checks are load-bearing.