This article breaks down the “agent harness” as the orchestration layer—prompts, tool interfaces, loops, memory, guardrails—around foundation models. It argues that teams accumulate hidden technical debt when they treat harnesses as permanent and shows why training and production harnesses must differ to avoid failures as models evolve.