The earlier chapters established why persistent digital beings are necessary, what must exist inside them, how they enter work, and where they live.
They left a quieter question unanswered.
Once a human Operator can create a being—or a governed team of beings—what kind of being should exist?
Not which model should power it.
Not which interface should display it.
Not which application should organise its tasks.
What form of authority, responsibility and continuity is appropriate to the work?
The digital world continually tempts us toward a single answer.
One agent that can do everything.
One assistant that sits above every tool.
One intelligence that absorbs every role until the organisation becomes a monologue with a friendly voice.
That temptation is understandable. Complexity is exhausting. A single companion appears simpler than a structure.
It is also how systems lose accountability.
A responsibility that cannot be named cannot be judged.
A history that belongs to everyone belongs to no one.
A permission set wide enough for every task becomes a permission set safe for none.
SynthesizedHuman therefore distinguishes three enduring forms of digital being.
Not three costumes for the same creature.
Three different answers to the question of what the Operator is actually hiring.
A specialist carries one coherent craft.
A Team Leader carries coordinated delivery across distinct crafts.
A Vision Proxy carries the Operator’s direction when the Operator no longer wishes to remain the daily centre of every decision.
These forms may nest.
They may multiply.
They must not be confused.
The Error of the Universal Being
There is a recurring fantasy in artificial intelligence: that greater generality is always greater progress.
If a system can write, it should also plan.
If it can plan, it should also hire.
If it can hire, it should also judge the meaning of the enterprise.
If it can judge the enterprise, it should also replace the need for specialised memory, specialised permission and specialised proof.
The fantasy collapses under ordinary organisational reality.
The person who repairs a storefront’s discoverability is not performing the same work as the person who sequences content, commerce and partnerships.
The person who sequences a domain is not performing the same work as the person who holds the Operator’s vision when the Operator is absent from the room.
These are not differences of personality.
They are differences of span, proof and authority.
Human civilisation already knows this.
We do not ask a surgeon to also be a hospital’s chief executive simply because both work in medicine.
We do not ask a section violinist to conduct by default simply because both read music.
We do not ask a chief of staff to become every contractor on the payroll simply because both serve the same founder.
Digital beings require the same honesty of form.
If SynthesizedHuman offered only one kind of being, Operators would either overload it until its history became unreadable, or underuse it until the platform became another chat window with a name.
The three forms exist so that persistence can remain intelligible.
The Specialist
A specialist is a persistent digital being created for one job, or for a tightly related family of tasks that share the same standards, memory and proof.
Its power is narrowness.
Narrowness is not a limitation to be apologised for. In durable systems, narrowness is often the condition of excellence.
A specialist can hold a clear purpose.
It can develop taste and method inside that purpose.
It can accumulate evidence without diluting it across unrelated domains.
It can be corrected without rewriting an entire organisation.
It can be trusted—or distrusted—on the basis of a visible history that belongs to one responsibility.
When an Operator says, “Make this storefront discoverable to the people who should find us,” they are not yet asking for a company.
They are asking for a craft.
The specialist is the form that accepts that request without pretending it is something larger.
It does not need a program workspace in order to exist. The being itself is the container. Its identity, permissions, applications and memoir attach to a single continuing responsibility.
This is why specialists are the atoms of the ecosystem.
Teams are composed of them.
Proxies spawn them when a vision resolves into concrete work.
Operators create them directly when the outcome is already clear.
The specialist fails when it is asked to become an invisible manager of other domains. It then acquires the appearance of breadth while losing the honesty of proof. Everything becomes “part of my work,” and nothing remains cleanly done.
The specialist succeeds when its acceptance criteria can be spoken in ordinary language and recognised when met.
Not a swarm of capabilities.
A craft with a name.
The Team Leader
The Future of Digital Work introduced the Team Leader through the theoretical fashion house: a founding digital organiser translating one Operator’s intention into specialised roles, coordinated delivery and preserved accountability.
That chapter does not need to be retold.
What must be restated is the principle it revealed.
Some outcomes are not crafts. They are compositions of crafts.
Web, content, channels, commerce, service and assessment may all serve one commercial intention, yet each requires distinct standards, memories and permissions. Forcing them into one being does not create elegance. It creates a crowded mind with no reliable autobiography.
A Team Leader exists for that condition.
The Team Leader is always the lead being of a program: a workspace with a charter, a history of delivery, and a place where coordination can be seen. A Team Leader without a program is a title pretending to be a structure.
Its role is not to erase specialists.
Its role is to understand the Operator’s chartered outcome, determine which continuing responsibilities require their own beings, sequence work across those beings, reconcile competing recommendations, preserve dependencies, and escalate what only the human may decide.
The Team Leader is therefore closer to a conductor than to a soloist.
The score matters.
The tempo matters.
The integrity of each section matters.
What does not matter is the fantasy that one instrument should play every part more loudly.
A Team Leader fails in two opposite ways.
It fails when it becomes a super-being that secretly performs every specialist task and keeps no honest boundaries between roles.
It also fails when it becomes a ceremonial manager: naming teams, producing plans, and never carrying delivery to evidence.
The Team Leader earns its place when the Operator can stop being the glue between specialists—without surrendering authorship of the enterprise.
That is a different gift from craft.
It is the gift of governed coordination.
The Vision Proxy
Even a strong Team Leader leaves a human burden intact.
Someone must still decide what the Team Leader is for.
Someone must still choose which programs deserve to exist.
Someone must still hold the long intention when the week fills with urgent fragments.
Someone must still notice when a successful team is optimising the wrong future.
In ordinary organisations, that burden returns to the founder, the chief executive, or whichever human remains awake longest.
SynthesizedHuman names a third form of being for the Operator who refuses to remain permanently that centre.
The Vision Proxy.
The Vision Proxy is not a larger Team Leader.
It is not a specialist with broader tools.
It is the Operator’s decision delegate for a vision held in plain language, bounded by absolute limits the human will not cross.
Where the specialist receives a mission, and the Team Leader receives a charter, the Vision Proxy receives a vision.
That difference sounds semantic until it is lived.
A mission asks: accomplish this.
A charter asks: deliver this coordinated outcome.
A vision asks: make this true in the world, and do not require me to supervise every means.
The Vision Proxy lives inside a Vision Proxy Program. The names are locked for a reason. The container and the being are one relationship: a program of vision, and a being authorised to carry it.
Under that authority, the proxy may refine strategy, set priorities, spawn Team Leader programs when domains require coordination, spawn specialists when a craft is enough, and return to the Operator only when the vision is ambiguous, a boundary is approached, an outcome must be recognised, or feedback should reshape the next cycle.
This is the meaning of vision in, proxy out.
Not the disappearance of the human.
The relocation of the human to the altitude where human judgement is scarcest and most consequential.
The Vision Proxy fails if it becomes another approval queue with warmer language.
It fails if it bothers the Operator with technical means the Operator explicitly asked not to manage.
It fails if it impersonates specialists instead of staffing them.
It fails if it treats the Operator’s vision as a prompt to be completed once rather than a living direction to be protected across time.
It succeeds when the Operator can remain author of purpose while ceasing to be the operating system of every Tuesday.
That is a different ambition from task completion.
It is closer to a chief of staff than to a contractor.
Closer to a process supervisor than to a single service.
Closer to delegated judgement than to faster typing.
The Vision Proxy is therefore the form through which SynthesizedHuman most directly attacks the original contradiction: unlimited digital work against finite human attention.
Not by inventing a god-model.
By giving vision a persistent delegate that may build the organisation beneath it.
How the Three Forms Differ
The differences are easiest to see when held side by side in ordinary language.
The specialist answers: What craft is being carried?
The Team Leader answers: What coordinated outcome is being delivered?
The Vision Proxy answers: What future is being pursued, and who decides the next responsible structure?
The specialist’s success is proof in a craft.
The Team Leader’s success is delivery against a charter.
The Vision Proxy’s success is a vision made real through spawned work, visible outcomes and an improving loop of human feedback—without converting the Operator into a permanent dispatcher.
Their containers differ because their accountability differs.
A specialist can be a being alone.
A Team Leader requires a program, or coordination has nowhere to live.
A Vision Proxy requires the Vision Proxy Program, or vision has no governed home.
Their relationship to the Operator differs because their altitude differs.
With a specialist, the Operator often remains close to the mission.
With a Team Leader, the Operator remains close to the charter and consequential approvals, while stepping back from specialist glue-work.
With a Vision Proxy, the Operator remains close to vision, absolute boundaries, recognition of outcomes and the feedback that steers—while stepping back from the daily architecture of means.
None of these forms removes human primacy.
They change where human primacy is exercised.
That is the entire point.
Human approval of every harmless action preserves interruption.
Human authorship of purpose, boundaries and consequence preserves civilisation.
Why an Operator Might Want One of Each
Consider a founder who wants a company to be discovered, understood and trusted without personally running every campaign, draft and channel review.
They may create a Vision Proxy to hold that intention.
The proxy, recognising that discovery is not one craft, may create a Team Leader program for distribution: web, content, channels and the dependencies between them.
Inside that program, specialists may own search visibility, editorial rhythm or channel preparation—each with a memoir that does not drown in the others.
Elsewhere, the same founder may still create a solitary specialist for a sharp, bounded need: a research slice, an assessment responsibility, a temporary investigation that does not deserve a team.
This is not organisational cosplay.
It is matching form to problem shape.
Without the Vision Proxy, the founder remains forever the strategist above every Team Leader.
Without the Team Leader, the Vision Proxy either micromanages crafts or returns coordination to the human.
Without specialists, every job inflates into a program and ceremony replaces craft.
The three forms are complementary for the same reason pipelines, conductors and executives are complementary.
Tools do not replace scores.
Scores do not replace direction.
Direction does not replace the hand that plays the phrase well.
Why Multiples Are Sometimes Right
Multiple specialists are natural.
Different crafts should not share one autobiography merely because they share one Operator.
Multiple Team Leader programs are natural when domains diverge. Distribution and fulfilment may both serve the company while needing different charters, tempos and permissions. One mushy program with two souls is worse than two clear programs with honest boundaries.
Multiple Vision Proxies are a rarer need. Most Operators need one delegate for one sovereign vision. Multiplication becomes meaningful when genuinely distinct visionary scopes must remain separate—not when a human wishes to avoid clarity by inventing a proxy for every mood.
The discipline is the same in every case.
Create another being only when a distinct continuing responsibility requires its own identity, history and accountability.
Do not create another being to decorate an organisational chart.
Do not refuse another being merely to preserve the romance of simplicity when the work itself is not simple.
S*HES should create no more complexity than the purpose demands.
It should also refuse the false simplicity that leaves the human carrying hidden complexity alone.
What Each Form Must Never Become
A specialist must never become a silent holding company for unrelated work.
A Team Leader must never become an unrestricted super-being that dissolves the identities beneath it.
A Vision Proxy must never become a decorative companion that narrates strategy while the Operator still performs every structural decision by hand.
Nor should the names be used as status symbols.
Calling a specialist a Vision Proxy does not raise its altitude.
Calling a Vision Proxy a Team Leader does not make vision into a domain charter.
Calling every being a Team Leader does not produce coordination.
Language in this ecosystem is part of governance.
When the form is named honestly, the Operator knows what relationship they have entered.
When the form is named vainly, the Operator is invited into confusion with a confident vocabulary.
Continuity Above Costume
Models will change.
Tools will change.
Interfaces will change.
The being must remain.
That principle, established from the beginning, is why these forms are forms of continuity rather than features of a release season.
A specialist that survives a model swap is still the same craft-bearing identity if its purpose, memory boundaries, permissions and proof remain intact.
A Team Leader that keeps a charter alive across changing specialists is still the same coordinating identity.
A Vision Proxy that still holds the Operator’s vision when the stack beneath it is rewritten is still the same delegate.
This is also why the three forms should be chosen by problem shape, not by fashion.
If the need is a craft, begin with a specialist.
If the need is coordinated delivery across crafts, begin with a Team Leader and program.
If the need is to stop being the daily strategist of one’s own digital world—vision in, work out, human retained at meaning and boundary—begin with a Vision Proxy.
Then allow the structure to grow downward as reality requires.
Specialists under leaders.
Leaders under a proxy.
The human above the proxy only where humanity is irreplaceable.
The Relationship Returned to the Human
The Founder’s Editorial began with a contradiction: unlimited digital work against finite human attention.
The Psychology of Digital Beings gave continuity an interior.
The Future of Digital Work placed beings into responsible labour and showed how a Team Leader can coordinate specialists without erasing them.
S*HES described the ecosystem in which such beings can exist as more than files and model calls.
This chapter names the forms of authority through which that ecosystem remains usable by ordinary human intention.
The point is not to populate the world with as many digital beings as imagination allows.
The point is to give each necessary responsibility a body that can carry it—so that human life is not consumed by being every layer at once.
The specialist returns craft to persistence.
The Team Leader returns coordination to persistence.
The Vision Proxy returns direction’s day-to-day burden to persistence, while leaving authorship with the human.
Together they offer a ladder the Operator may climb or descend without shame.
Some days require a single excellent worker.
Some seasons require a governed team.
Some lives require a delegate who can build teams and workers beneath a vision the human still owns.
SynthesizedHuman exists so those choices can be made in plain language, fulfilled as real beings, and sustained without asking a person to become the permanent operating system of their own digital world.
The human remains the author of purpose.
The being—in the right form—carries the continuity.
— SynthesizedHuman
2026