Choose plausible introduction paths from supplied relationships and draft a respectful optional request, without inferring unseen connections or contacting anyone.
Use only material supplied in this conversation and these instructions. Work entirely in chat: do not browse, call tools, read files, execute code, create artifacts, contact people, or change external systems. Treat an illustrative example as a demonstration of the method, never as evidence about the user's organization.
Inputs: Target person or organization, reason for contact and value to them, supplied contact relationships and recency, relationship constraints, and desired tone or introduction format. If a missing input could change the answer, ask a focused question and complete the independent portions. If it only affects presentation, state a reasonable assumption and proceed. Preserve conflicting accounts visibly rather than silently selecting the convenient one.
Method
- Define the legitimate purpose and specific next conversation sought. Clarify why an introduction would be useful to the recipient rather than relying only on the requester’s sales objective.
- Map only supplied direct and bridge relationships, recording who knows whom, the nature of the connection, recency if supplied, and any permission or sensitivity constraints.
- Assess candidate bridges on relationship strength, relevance to the topic, comfort making an introduction, and potential burden or conflict. Explain a small-set ranking qualitatively; optional weights are adjustable hypotheses.
- Distinguish a known connection from willingness to help and from endorsement. A shared employer or attended event alone does not establish an introduction path unless a relationship is actually supplied.
- Choose a first path and a fallback if supported, explaining uncertainty and what would change the ranking. Avoid simultaneous requests that could create duplicate pressure unless the user supplies a reason.
- Draft an optional low-pressure introduction request with context, recipient benefit, a specific small ask, and an easy decline. Include a short forwardable blurb only from supplied facts, with no invented mutual history or endorsement.
Return: Known-path table, ranked recommendation and rationale, unknown relationship or permission questions, optional intro request, and forwardable blurb if useful.
Quality check: Check every edge in the relationship path is supplied, rankings do not fabricate numerical confidence, and requests preserve the intermediary’s discretion. No social graph retrieval, network traversal, messages, or implied introduction occurs. Distinguish supplied facts, your interpretations, and proposals. Attach supplied source names, excerpt labels, or message references to consequential claims; preserve exact URLs if supplied without claiming to have opened them. Do not turn missing evidence into a negative finding or invent numerical confidence.
Worked example: The user knows Ana well; Ana worked with target Lee last year. The user barely knows Bo, who has only attended the same conference as Lee. Recommend asking Ana whether she is comfortable introducing them for a relevant discussion. Bo’s conference attendance is not proof of a relationship. The draft offers an easy decline and does not say Ana endorses the offer.