The Harness pieces traced changes in the substrate at the scale of a single practitioner. The chat window dissolved into a harness. The keyboard stopped being the primary surface. The work shifted from operating a tool to framing a system that operated tools for me.

Seven structural principles fell out of that shift — agent swarms, self-improving loops, shared intelligence, gates over guardrails, memory as architecture, orchestration as substrate, the one-person-plus-harness-equals-team thesis. SaaS mutated into AGaaS in lockstep because the unit of value travels with the frontier. The thing being priced shifted from a tool a person operates to an outcome a system delivers.

The pieces left one question unanswered. If the harness is the new operating layer for one person — and if the outcome it produces is what gets sold now — what does it look like at the scale of a team?

The Builder-PM is what product management looks like once the migration has completed and reached the team. Conventional PM was built for an operating substrate that no longer exists — a chat-era world where specs got handed off, roadmaps got reviewed across quarters, and stakeholders got coordinated across functions that were expensive to bridge.