Repository navigation
feat: Introduce — introduce your contacts to people on Index, through you - #1927
Merged
Merged
Conversation
…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>
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
opportunity_proposals.viathe introducer (OpportunityActor.via;networkIdis now optional).Protocol / API changes
OpportunityActor.networkIdoptional, newOpportunityActor.via.viaseats side B by owner alone.viaparticipant./api/auth/link-socialis forwarded to better-auth./introducer/*routes andIntroducerCron.Migrations
0021contacts,0022card embeddings,0023opportunity_proposals+contacts.excluded_at(carries existing rows over),0024dropsintro_suggestions. Already applied to the dev database.Before it works on an environment
contacts.readonlyandcontacts.other.readonly, and the API's/api/auth/callback/googleas a redirect URI.PARALLELS_API_KEY(research on wake; without it the seat is built from the contact card).Verified
intro-desk-previewRailway env, against the dev database: contact sync, background matching (94 real proposals from one account), and opening avia-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.🤖 Generated with Claude Code