Referral or Collaboration Protocol¶
Routing protocol — instantiates Domain-Specificity of Confidence
Routes a claim that has left validated scope to whoever holds stronger warrant, making the handoff the normal move rather than a concession.
A Referral or Collaboration Protocol is a standing procedure that, when a claim falls outside an actor's warrant, routes it to stronger warrant — an in-domain expert, a collaborator, or a joint decision — through a pre-defined pathway, and treats that handoff as the default professional move. Its defining feature is that it doesn't merely flag the boundary or lower confidence; it supplies the missing competence by moving the claim to someone who has it, and it makes doing so socially normal rather than an admission of weakness. This is what keeps epistemic humility actionable: instead of the decision stalling at "not my area," it still gets made — well.
Example¶
A general-practice attorney's client mentions a cross-border tax question buried in an estate matter. The firm's protocol is explicit: a question outside your practice area routes to the tax group, or to named outside counsel, and the engagement letter and billing structure already accommodate the handoff. So the referral is frictionless and expected — the generalist introduces the specialist, the client gets stronger warrant on the tax question, and the generalist keeps the overall relationship and credit for the referral. The move maps directly onto the professional idea of scope of practice: you operate confidently inside your licensed competence and route what lies beyond it.[n1]
How it works¶
- Maintain a routing table. Which target domain maps to which expert, partner, or team — kept current so a handoff doesn't require a scramble.
- Define the trigger and the handoff mechanics. What condition routes a claim (an out-of-scope determination, or a fired interrupt), and how the handoff happens: a warm introduction, a co-sign, or joint sign-off.
- Pick the target by warrant, not availability. The protocol selects whoever actually holds stronger warrant in the target domain, not merely who is free — reading a warrant record rather than a calendar.
- Institutionalize the norm. The protocol's real work is cultural: opting to refer is respected and rewarded, so status pressure to answer everything oneself meets an easy, high-status alternative.
Tuning parameters¶
- Routing granularity — refer the whole claim vs. collaborate on the out-of-scope part; whole-claim referral is cleaner, collaboration keeps the referrer engaged.
- Trigger tightness — route on any out-of-scope claim vs. only high-stakes ones; tighter triggers refer more and can feel like offloading.
- Target-selection rule — by measured warrant vs. seniority vs. availability; warrant-based routing is best but demands a warrant record to read.
- Handoff depth — full referral vs. co-decision vs. an informal curbside consult; deeper handoffs transfer more warrant and cost more coordination.
- Incentive alignment — how credit and billing follow a referral; if referring costs the referrer, the protocol quietly stops being used.
When it helps, and when it misleads¶
Its strength is unique among the siblings: it is the only mechanism that supplies the missing warrant rather than merely withholding confidence, so a claim outside anyone's scope still reaches a competent decision.
Its failure is buck-passing — routing a claim to shed accountability rather than to serve it — and the mirror failure of a culture where referral is read as weakness, so it is quietly avoided and overreach persists. The classic misuse is gatekeeping: routing to protect territory or bury a claim in committee. The guarding discipline is to align incentives so referral is credited, not penalized, and to keep a light audit confirming that routed claims actually land on stronger warrant rather than disappearing into a queue.[n1]
How it implements the components¶
The protocol fills the routing side of the archetype — moving a claim to competence:
expert_referral_pathway— its core: the routing table and handoff mechanics that carry an out-of-scope claim to an in-domain expert or collaborator.warrant_inventory— it reads who holds stronger warrant in the target domain in order to choose the right referral target rather than the nearest one.status_pressure_guardrail— by making the handoff the default, respected move, it strips the status cost from not answering oneself.
The protocol executes a handoff but does not itself detect the overreach or decide the halt-and-relabel response. The rule that decides to downgrade a breaching claim — confidence_downgrade_rule — belongs to the Out-of-Domain Prompt, its nearest twin: the prompt decides to downgrade, while this protocol carries out one particular downgrade response, the referral.
Related¶
- Instantiates: Domain-Specificity of Confidence — the protocol is the "route or update" step that keeps a scope-limited actor useful.
- Consumes: Out-of-Domain Prompt supplies the trigger that a claim has left scope; Track Record by Domain Scorecard supplies the warrant record used to pick the target.
- Sibling mechanisms: Expertise Scope Matrix · Claim Confidence Labeling · Out-of-Domain Prompt · Track Record by Domain Scorecard · Transfer Assumption Review · Confidence Retrospective
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Referral or Collaboration Protocol operates as a repeatable ordered procedure or handoff sequence that coordinates action because it routes a claim that has left validated scope to whoever holds stronger warrant, making the handoff the normal move rather than a concession.
Independent corroboration: The frozen evidence defines Referral or Collaboration Protocol as 'Routes a claim that has left validated scope to whoever holds stronger warrant, making the handoff the normal move rather than a concession', so its operative form is Protocol, Workflow & Routine.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Medicine & Healthcare
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Professional referral when a case exceeds validated competence is canonically institutionalized in healthcare.
Related originating lineages:
- Organizational & Management Science — Expertise routing and cross-functional handoff materially generalize referral beyond clinical practice.
Review resolution: Both blind reviewers agree that medicine_healthcare is the primary origin. Explicit reconciliation of alternate origin disagreement, origin mode disagreement, encyclopedia synthesis disagreement adopts reviewer_a's classification because professional referral when a case exceeds validated competence is canonically institutionalized in healthcare. The resulting lineage records alternates=organizational_management, origin_mode=cross_disciplinary_synthesis, and domain_reach=multi_domain; these describe formative provenance separately from later applicability.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] Scope of practice is the professional and regulatory concept defining the procedures, actions, and decisions a licensed practitioner is competent and authorized to perform. It normalizes referral: operating confidently within one's scope and routing beyond it is treated as competence, not deficiency — the cultural stance this protocol tries to install. ↩a ↩b