There's a particular kind of dismissal I've gotten used to. A typical response to the idea of harness engineering being a legitimate field of engineering, and not just a matter of typing the right words. The framing is wrong, and I want to say why. What engineering actually is Engineering isn't defined by its substrate. It's not what you do to silicon, or to bridges, or to pipelines. Engineering is the disciplined application of the scientific method to building things that work. You form a hypothesis about the world, you make a change to test it, you observe the result, and you keep what survived and discard what didn't. Do that long enough on the same artifact and you end up with something that embodies a stack of accepted theories about how its inputs map to its outputs. That description fits what I do on the harness exactly. The loop I have a system prompt. I have a set of tools. I have a corpus of inputs, rules, skills, and so on. I have outputs. When I make a change to the harness, I am not vibing.…