Build the harness, buy the commodity — note 146

Build the harness, buy the commodity — note 146 sounds like a strategy slide until you watch a team try it under real load.

A purchased AI tool still needs an owner on-call for failure modes, data handling, and process fit.

Buy commodities. Build the harness that makes your team’s judgment visible: policy, evals, audit, and exit.

Cross-team collaboration gets easier when you publish interfaces: who consumes what, what “done” means, and how failures are communicated. Ambiguity is expensive; clarity is a kindness.

Make-or-buy decisions should include the cost of undoing the choice. Soft lock-in is still lock-in.

AI compresses the typing cost of building. It does not compress the ownership cost of running what you built.

In practice that means shorter cycles: decide, ship a thin slice, review what broke, coach the pattern into the next person. Long programs without those loops become status machines.

On build the harness, buy the commodity — note 146, the leadership move is to make the invisible visible: ownership, verification, and the path for the next person.

Mentorship scales when seniors narrate tradeoffs in writing. A one-paragraph decision record teaches more than a hallway conversation that evaporates.

Team literacy matters more than individual clever prompts. Shared harnesses beat private magic.

I prefer written decisions over verbal ones. Memory is a poor archive, and AI tools make fluent improvisation cheap — which raises the value of durable context.

None of this requires a new framework brand. It requires attention, a short feedback loop, and the humility to change process when agents join the workflow.

Ask your team one question in standup this week: what did we make easier to own?