Skip to content

feat: Introduce — introduce your contacts to people on Index, through you - #1927

Merged
serefyarar merged 13 commits into
devfrom
preview/intro-desk
Nov 20, 2026
Merged

serefyarar merged 13 commits into
devfrom
preview/intro-desk

Conversation

@serefyarar

Copy link
Copy Markdown
Contributor

Introduce (Intro Desk)

A member introduces people in their networks to people they know who aren't on Index. The page is /introduce (menu: introduce). Docs: /use/introduce.

Reach rule. Index reaches a person through a network (discovery) or one hop through a person (an introduction), never chained. A contact is reached only through the member who knows them: their seat is in no network, discovery never returns it, and nobody else can reach it.

What's in it

  • Contacts. Connect Google (saved contacts + "other contacts"). Synced on connect, then again when the page is opened and the last sync is over a day old. Contacts tab: search, filter, never suggest, delete all.
  • Proposals. A background pass every 2 minutes embeds contact cards and matches each new public intent against the contacts (not on Index) of members who share its network. Newly synced contacts are matched the other way. One LLM screen keeps real fits and writes the card lines and a draft intro. Proposals are opportunities nobody has opened yet, in the opportunity format, stored in opportunity_proposals.
  • Waking. Looks the contact up on the public web (Parallel), seats them as an unverified account with intents in no network, and opens the opportunity with the member's agent first. The contact's actor is anchored via the introducer (OpportunityActor.via; networkId is now optional).
  • After. When the member says yes, the contact gets one email in the introducer's name. If the introduction ends without a match, what research found is removed.
  • Feedback. The introducer sees status only (talking, agreed, met, no fit, went quiet), never turns or who said no.

Protocol / API changes

  • OpportunityActor.networkId optional, new OpportunityActor.via.
  • Negotiation adapter: a pair with via seats side B by owner alone.
  • Intent-scoped opportunity list accepts a via participant.
  • /api/auth/link-social is forwarded to better-auth.
  • New /introducer/* routes and IntroducerCron.

Migrations

0021 contacts, 0022 card embeddings, 0023 opportunity_proposals + contacts.excluded_at (carries existing rows over), 0024 drops intro_suggestions. Already applied to the dev database.

Before it works on an environment

  • Google Cloud OAuth client: People API enabled, scopes contacts.readonly and contacts.other.readonly, and the API's /api/auth/callback/google as a redirect URI.
  • API env: PARALLELS_API_KEY (research on wake; without it the seat is built from the contact card).

Verified

  • On the intro-desk-preview Railway env, against the dev database: contact sync, background matching (94 real proposals from one account), and opening a via-anchored opportunity with my own intent and a made-up seat. It showed in the member's intent-scoped and full lists, not in the network-bound list, and the introducer saw "talking". Test rows were deleted.
  • Not yet run end to end: wake → research → member yes → email → contact claims the seat by signing in.

🤖 Generated with Claude Code

serefyarar and others added 13 commits November 18, 2026 20:48
…ns, wake both agents

- contacts table (0021): a member's Google contacts and people they've
  emailed, matched to Index accounts; private to the owner
- /introducer API: status, contacts import (People API via the linked
  Google account), pair suggestions, introductions with progress
- pairs: other people's public intents in networks you share, at least one
  a contact, no negotiation yet; a model keeps the pairs where one can help
  the other and drafts the intro
- progress is the negotiation's shape only (turns, who moved, yes/no),
  never what the agents wrote
- web /introduce: setup (connect Google contacts, import), pair cards with
  an editable intro, "Wake both agents" via POST /opportunities, and a
  bottom-right progress panel with tabs and a minimize pill
- nav: "introduce" in the desktop rail and the mobile "you" sheet

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…tacts linking

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The introducer now sees an introduction's phase only (talking, agreed,
met, no fit, quiet): no turns, no whose-move, and a no fit never says
which side. Contacts re-sync from Google once a day in the background and
drop people removed there; the re-import button is gone.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The screen writes a six-word line per side completing '<name> …' (what
they need or bring); the card shows them left ⇄ right instead of quoting
both intents. Falls back to a clipped intent when the screen fails.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…works

An Intro Desk pair is now a member's public intent ⇄ one of your contacts
who is not on Index. Matching runs in the background: contact cards are
embedded once, each new public intent is matched against the contacts of
members who share its network, and newly synced contacts are matched the
other way; one LLM screen keeps real fits and writes the card lines and a
draft. The desk reads stored suggestions.

Waking a pair looks the contact up on the public web, seats them as an
unclaimed account in no network, and opens the opportunity with the
contact anchored via the introducer (OpportunityActor.via) instead of a
network: one hop, never chained, invisible to discovery. When the member
says yes the contact gets one email from the introducer; when it ends
without a match, what research found is removed.

Migration 0022: contact card embeddings and intro_suggestions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
/use/introduce: how reach works (through a network, or one hop through a
person, never chained), setup, pairs, waking, status-only progress, when
the contact hears, and who sees what. The diagram is an inline SVG that
follows the docs theme.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…mn desk

Proposals are opportunities nobody has opened yet, in the opportunity
format (detection, actors, interpretation, context, confidence,
metadata.introducer), kept in opportunity_proposals because an
opportunity row is born negotiating and the contact has no seat yet; the
contact's actor carries contactId and via until opening seats them.
Opening writes the real opportunity and links it.

Contacts tab: search, filter (on Index, not on Index, never suggest),
never-suggest per contact, and delete all. The running state moves from
the bottom-right popup into the page: pairs on the left, running and
done introductions on the right.

Migrations 0023 (opportunity_proposals, contacts.excluded_at, carries
existing suggestions over) and 0024 (drops intro_suggestions).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…tact rows

'emailed' meant Google's Other contacts (people you've emailed but never
saved); it moves to the row's tooltip. 'not on Index' repeated on almost
every row, so only 'on Index' is tagged. '1 pair' reads '1 pair waiting'.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Running is one row per introduction with home's status square (talking,
agreed, met, no fit, went quiet) instead of a 4-stop track each. Pair
cards drop their border and shadow; the intro label and input stay.
Section heads use home's double rule.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ing, shorter intro label

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@serefyarar
serefyarar merged commit cda26c3 into dev Nov 20, 2026
4 of 5 checks passed
@serefyarar
serefyarar deleted the preview/intro-desk branch November 20, 2026 04:57

This branch was previously deployed

1 inactive deployment
Index / intro-desk-preview — bd261f35 Deployed Nov 20, 2026 by railway-app[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant