The proxy idea was framed for specialists, but it was quietly true of the builder all along: the spec, the shared model, the fast lanes. Naming it ties the whole model together - even the central role obeys the same backbone: encode the codifiable middle, reserve the human for the edge.
01 - Encoded judgment
A specialist encodes domain judgment into a sub-agent. The builder encodes accumulated product judgment - spec, shared model, design system, taste - into the source of truth.
That substrate is a partial proxy of the builder. Two things follow, and both free the builder's calendar.
Instead of waiting, a stakeholder interacts with the encoded model and the build agents - which carry the builder's taste - and gets a fast feasibility-and-fit check: does this fit the product, is it possible the way I want, here's roughly how it looks. The builder's judgment, with the builder absent.
Self-serve and live co-creation both produce coherent output because the agents build from the builder's encoded patterns.
The fast lane isn't ungoverned - it's governed by the builder's encoded judgment.
02 - The engagement spectrum
Each piece of work takes the lightest mode that fits. The three modes differ only in how present the builder is.
Self-serve - no builder. Guardrails only.
Builder-proxy fast lane - the judgment, not the builder. The encoded judgment is present; the live builder is not.
Live co-creation - the builder. Present, for novel work.
Self-serve: no builder. Fast lane: the builder's judgment, not the builder. Live: the builder.
03 - Hardest to proxy
A specialist's domain judgment is bounded and largely codifiable. The builder's core value - novel intent, arbitration, deciding what the product should become - is precisely the un-encodable part.
So the builder-proxy covers a smaller fraction of its role than a specialist-proxy covers of theirs. It offloads the repetitive "can we do X / does X fit" traffic - a real chunk of a builder's day - and frees the builder for the generative frontier. It does not make the builder optional.
It offloads the "can we / does it fit" traffic. It does not make the builder optional.
04 - Two caveats
The proxy earns its place only if it stays honest about what it answers and how it survives.
The proxy answers "fits the product as it is." So "the proxy says this doesn't fit" has to be a routable escalation to the live builder - maybe the product should evolve - not a dead end. Otherwise it quietly enforces the cowpath bias, now at the product level.
Unlike a sidecar specialist agent, the builder's proxy is the spec and shared model - the builder's working medium - so every build refreshes it. It rots less, as long as the builder keeps building.
"The proxy says this doesn't fit" must be a routable escalation, not a dead end.
05 - Eating its own dog food
Even the central role obeys the backbone: encode the codifiable middle - the product model and taste - and reserve the human for the edge - novel product decisions.
Naming the builder as a proxy ties the whole model together. The rule that governs every specialist also governs the one role you might think exempt: the spec and shared model carry the builder's judgment so stakeholders can argue with it, while the un-encodable frontier stays human.
Even the central role obeys the backbone: encode the middle, reserve the human for the edge.
The builder's product judgment - spec, shared model, design system, taste - encodes into the source of truth, making that substrate a partial proxy stakeholders can argue with while the builder is absent. It sits as the fast lane between self-serve (no builder) and live co-creation (builder present), covers a smaller fraction of the role than a specialist-proxy does, must route "doesn't fit" as escalation rather than a dead end, and largely maintains itself because it is the builder's own working medium.