Proxy Mediation¶
Insert an intermediary that acts on behalf of another entity to reduce direct exposure, coordination burden, or dependency.
The Diagnostic Story¶
Symptom: Direct interaction exposes too much: the principal is overloaded by requests a bounded representative could handle, counterparties receive internal detail that creates security or leverage risk, and informal proxies have already appeared but with no clear authority, scope, or revocation path. Either the principal is held responsible for things the proxy did without authorization, or the proxy escapes accountability altogether.
Pivot: Introduce a proxy node with an explicit representation interface, delegation rule, authority scope, trust policy, accountability record, and revocation or escalation path — so it can mediate on behalf of the principal without becoming an unbounded substitute or opaque gatekeeper.
Resolution: The principal's exposure surface is bounded; routine interactions are handled by the proxy at lower cost; counterparties have a stable representative surface; and proxy actions are traceable for audit, correction, and dispute resolution. When the proxy's mandate is insufficient, exceptional cases can still reach the principal.
Reach for this when you hear…¶
[corporate legal] “The reason you have outside counsel speak to the regulator is precisely so you can control what leaves the building — if your CFO takes that call, you have no boundary left.”
[software architecture] “The whole value of an API gateway is that your downstream clients never know which microservice changed — if they call your services directly, any internal refactor breaks them.”
[diplomatic protocol] “An ambassador can receive a communication and ask for instructions rather than committing the state on the spot — that gap is not inefficiency, it is the entire point of having representation.”
When This Archetype Applies¶
Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.
Diagnostic problem
A direct relationship between a principal and counterparty is costly, unsafe, too complex, too revealing, too dependency-producing, or too burdensome, and at least one side can be represented by an intermediary without destroying the value of the interaction.
What this problem means
The structural problem is a costly direct edge. A principal and counterparty could interact directly, but the edge is too exposing, too noisy, too dependent, too trust-heavy, or too demanding. The principal may be a service, person, organization, resource owner, patient, client, team, or institution. The counterparty may be a caller, client, requester, adversarial environment, market, bureaucracy, or public audience.
Without a proxy, the principal is forced either to open itself directly or to refuse interaction. Direct openness creates leakage, overload, capture, inappropriate dependency, and repeated negotiation. Total closure blocks useful exchange. Proxy mediation creates a controlled substitute relation: the counterparty interacts with a representative, while the principal remains shielded or selectively reachable.
Show the applicability expression
Applicability expression5 distinct conditions
groundedpartly groundedopen
5 conditions, all required.
5Required in every casenumbered 1–5
These hold no matter which pattern applies.
Sensitive direct disclosure · open
Direct contact would reveal sensitive identity, state, capacity, credentials, structure, or intent.
The source archetype describes the situation as follows: Direct contact would reveal identity, location, internal structure, sensitive state, capacity, preferences, credentials, or strategic intent. The normalized requirement above isolates the load-bearing portion used in this condition set.
Direct-interaction incapacity · open
The principal lacks capacity, expertise, presence, standing, language, or protocol compatibility for direct interaction.
The source archetype describes the situation as follows: The principal lacks time, expertise, presence, standing, language, protocol compatibility, or procedural capacity to interact directly. The normalized requirement above isolates the load-bearing portion used in this condition set.
Stable opaque interface · open
The counterparty needs a stable interface while principal internals or availability remain hidden.
The source archetype describes the situation as follows: The counterparty needs a stable point of interaction, but the principal’s internal implementation, availability, or decision process should remain hidden. The normalized requirement above isolates the load-bearing portion used in this condition set.
Unsafe direct exchange · grounded
Trust risk makes direct exchange of value, information, access, or commitment unsafe.
The source archetype describes the situation as follows: Trust risk makes direct exchange unsafe because one party should not release value, information, access, or commitments directly. The normalized requirement above isolates the load-bearing portion used in this condition set.
Rigid direct dependency · grounded
Direct dependency would make later substitution, scaling, privacy, or governance difficult.
Direct openness creates leakage, overload, capture, inappropriate dependency, and repeated negotiation. The narrower requirement in this condition set is: Direct dependency would make later substitution, scaling, privacy, or governance difficult.
Other requirements and context (1)
Why these sit outside the expression
Deployment constraint — it constrains how the intervention must be deployed, not the situation that calls for it.
Deployment constraintThe principal needs representation but also needs authority limits, consent rules, traceability, and revocation.
The archetype is especially useful when a principal can define what the proxy may do and when counterparties can reasonably rely on the proxy’s authority. In this archetype, the relevant deployment constraint is: The principal needs representation but also needs authority limits, consent rules, traceability, and revocation. It identifies a boundary that responsible implementation must respect.
Coverage
2 of 5 conditions grounded · 3 open.
Mechanisms / Implementations¶
- Forward Proxy Server: Sits in front of a population of internal clients and makes their outbound requests for them, so the organization can control and record what its own users reach on the outside.
- Reverse Proxy Server: Receives external requests on behalf of a protected backend service, presents a stable public surface, and hides the origin's location and topology from callers.
- Human Agent or Representative: A person who speaks and acts for a fully-capable principal in dealings the principal chooses not to conduct directly, translating the principal's intent into the counterparty's terms.
- Broker Intermediary: Represents a principal in a market — finding counterparties and negotiating terms within a bounded mandate — so neither side has to deal, or over-expose itself, directly.
- Escrow Service: Holds money, assets, or keys in neutral custody during an exchange and releases them only when agreed conditions are met, so neither party has to trust the other directly.
- Guardian or Delegate Role: A person appointed to act for a principal who cannot act for themselves, bound by a fiduciary duty to decide in the principal's interest and subject to outside review.
- Power of Attorney or Mandate Document: A written instrument that records exactly what authority a principal grants a proxy, so counterparties can verify the scope and binding force of the proxy's actions.
- Service Account or Bot Delegate: A non-human machine identity that carries narrowly-scoped credentials to act for a principal automatically, with every action attributable and its credentials rotated or revoked when stale.
- Privacy Relay or Anonymizing Proxy: Relays a source's requests while stripping the identifying signals that would link them back, so a counterparty or observer sees the traffic but not who sent it.
- Cached Representation Service: Answers repeated requests on a principal's behalf from a stored copy of its representation, so the principal isn't touched for every interaction — as long as the copy is still fresh.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (3)
- Boundary: Defines system limits.
- Indirection: Introduces intermediary references.
- Network: Models interactions between components.
Also references 4 related abstractions
- Accountability: Responsibility for actions.
- Governance: The durable architecture of authority, accountability, and decision rights through which a group makes binding collective choices and resolves disputes internally.
- Topology: Studies properties preserved under deformation.
- Trust: Willingly accepting vulnerability to another party's future behavior under incomplete monitoring, based on positive expectations about their competence and intentions.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Forward Proxy Mediation · implementation variant · recognized
A proxy acts on behalf of a requester or client when interacting with external systems, counterparties, or environments.
Reverse Proxy Mediation · implementation variant · recognized
A proxy acts on behalf of a protected service, resource, institution, or principal when receiving requests from external parties.
Agent Representation · governance variant · recognized
A person, team, or institution acts as an authorized representative for a principal in communication, negotiation, or decision contexts.
Escrow Mediation · mechanism family variant · recognized
A trusted intermediary temporarily holds assets, commitments, keys, information, or value and releases them under defined conditions.
Brokered Proxy Mediation · governance variant · candidate
A broker mediates on behalf of one or more parties by representing needs, matching counterparties, negotiating conditions, or reducing exposure.
Editorial Notes¶
Problem Classification¶
Classification: Composition, Interface & Interoperability Failure → Coupling, Topology & Transfer Mismatch
Problem kernel: a costly direct relationship needs mediated coupling
Rationale: Earliest causal condition: A direct relationship between a principal and counterparty is costly, unsafe, too complex, too revealing, too dependency-producing, or too burdensome, and at least one side can be represented by an intermediary without destroying the value of the interaction.
Independent corroboration: The earliest necessary condition in the frozen evidence is: A direct relationship between a principal and counterparty is costly, unsafe, too complex, too revealing, too dependency-producing, or too burdensome, and at least one side can be represented by an intermediary without destroying the value of the interaction. That is a coupling topology and transfer mismatch problem because Connections exist at the wrong intensity, direction, arrangement, gradient, or impedance, or a needed bridge is absent between otherwise viable parts.
Review outcome: Independent reviewer agreement; medium confidence.