@gonzih/meet-the-one-ai 1.0.0 → 1.0.1

package/.env.example

@@ -1,41 +1,18 @@
-# Supabase
-SUPABASE_URL=https://your-project.supabase.co
-SUPABASE_SERVICE_ROLE_KEY=your-service-role-key
+# Telegram
+TELEGRAM_BOT_TOKEN=
 
-# Twilio
-TWILIO_ACCOUNT_SID=ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
-TWILIO_AUTH_TOKEN=your-auth-token
-TWILIO_VERIFY_SERVICE_SID=VAxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
-TWILIO_NUMBER_FLAGSHIP=+1xxxxxxxxxx
-TWILIO_NUMBER_CASUAL=
-TWILIO_NUMBER_KINK=
-TWILIO_NUMBER_ADVENTURE=
-TWILIO_NUMBER_OPEN_POLY=
+# Redis
+REDIS_URL=redis://localhost:6379
 
-# Vapi (voice AI — v0.1)
-VAPI_API_KEY=your-vapi-key
-VAPI_INTAKE_ASSISTANT_ID=your-intake-assistant-id
-VAPI_CONSENT_ASSISTANT_ID=your-consent-assistant-id
-
-# Anthropic
+# Anthropic (for Claude Code subprocess)
 ANTHROPIC_API_KEY=sk-ant-xxxxx
 
-# OpenAI (embeddings)
-OPENAI_API_KEY=sk-xxxxx
-
-# Deepgram (transcription)
-DEEPGRAM_API_KEY=your-deepgram-key
-
-# Cloudflare R2
-CLOUDFLARE_ACCOUNT_ID=your-account-id
-R2_ACCESS_KEY_ID=your-access-key
-R2_SECRET_ACCESS_KEY=your-secret-key
-R2_BUCKET_NAME=meet-the-one-audio
+# Claude Code OAuth token (alternative auth)
+CLAUDE_CODE_OAUTH_TOKEN=
 
-# Inngest
-INNGEST_EVENT_KEY=your-event-key
-INNGEST_SIGNING_KEY=your-signing-key
+# BlueBubbles (iMessage delivery)
+BLUEBUBBLES_URL=http://localhost:1234
+BLUEBUBBLES_PASSWORD=yourpassword
 
-# App
-APP_URL=http://localhost:3000
-PORT=3000
+# System phone number (for iMessage sender identity)
+SYSTEM_PHONE_NUMBER=+1XXXXXXXXXX

package/SPEC.md

@@ -0,0 +1,202 @@
+# Meet The One AI — Product Spec
+
+**North star:** Life as adventure. Expand the journey. Soul x-ray at global scale.
+
+---
+
+## The Problem
+
+Dating apps are slot machines. Swipe, match, ghost, repeat. The mechanism is engineered for engagement, not connection.
+
+The real problem: **compatibility is complex and humans are bad at self-knowledge.** People say they want one thing, respond to another, need a third. A 30-question quiz can't map that. 1000 swipes can't either.
+
+What could: an agent that actually knows you — not your curated self, your real self — watches how you respond, and works on your behalf.
+
+---
+
+## The Vision
+
+Phone = identity anchor. Soul x-ray. Unconscious psyche captured through conversation, compacted into identity, matched globally.
+
+**No photos. No swiping. No appearance data at any point.**
+
+Introduction via system-initiated contact. The iMessage blue bubble IS the introduction — it feels like a person thought of you.
+
+---
+
+## The Product
+
+An AI matchmaker that operates as your personal agent.
+
+Not a dating app. Not a chatbot. An agent — a Claude Code instance running on your behalf — that:
+
+1. Gets to know your real inner world through projective conversation (not a form)
+2. Captures the unconscious self: what you avoid, what lights you up, what scares you
+3. Compacts everything into a dense identity with worldview anchors and modality weights
+4. Matches globally across profiles — vector similarity + hard worldview gates
+5. Reaches out directly via iMessage when it finds your person
+
+**The experience:**
+- You talk to your agent. It asks real questions — projective, not direct.
+- It listens for what you don't say as much as what you do.
+- When it finds a candidate: blue bubble. "I found someone."
+- You never see a profile grid. You never swipe.
+- You either get introduced to someone real, or you don't hear from your agent that day.
+
+---
+
+## Architecture — cc-tg Pattern
+
+Every user has a **persistent Claude Code subprocess** as their intake and matchmaker agent.
+
+```
+User (Telegram)
+  └── Their personal Claude Code session
+        └── MCP tools (soul x-ray domain)
+              ├── create_profile (phone_number required — identity anchor)
+              ├── log_intake_response (question, response, modality)
+              ├── update_worldview (dangerous/adventurous, good/bad)
+              ├── get_soul_profile (completeness score + full identity)
+              ├── send_intro_message (BlueBubbles → iMessage blue bubble)
+              ├── schedule_introduction_call
+              ├── request_match / respond_to_match
+              └── get_matched_pairs
+
+Matching Engine (separate process, Inngest)
+  └── Runs when identity updated
+  └── pgvector search → worldview hard filter → LLM validation
+  └── On match confirmed: initiate iMessage introduction to both phones
+```
+
+---
+
+## The Big Sorts (Non-Negotiable)
+
+Two questions split the user population into incompatible universes:
+
+1. **Is the world fundamentally a dangerous place or an adventurous place?**
+2. **Do you think people are fundamentally good or fundamentally bad?**
+
+A person who answers dangerous + bad will not be matched with someone who answers adventurous + good. This is a hard gate in the matching engine — not a soft preference.
+
+---
+
+## Intake — Soul X-Ray
+
+The intake agent NEVER asks direct questions. It reaches for the unconscious.
+
+**Projective prompts:**
+- "Close your eyes. Imagine a big white empty space. What's the first thing that comes to mind?"
+- "Imagine a big empty black space. What do you feel?"
+- "Tell me about a moment you felt completely free."
+- "What are you most afraid of in another person?"
+
+**Behavioral signals (gathered indirectly):**
+- Do they travel? Do they have a passport?
+- Are they a yes-person or a no-person?
+- How do they text — punctuation style, response latency, emoji?
+
+**The 4AM principle:** Encourage voice messages late at night, when defenses are down and the real self speaks. Every voice session is transcribed and analyzed as signal.
+
+---
+
+## Introduction Flow — The Blue Bubble
+
+When two users match and both consent:
+
+```
+System → iMessage to User A:
+"hey [name] — i've been thinking about this.
+i found someone. their name is [name].
+i'm not going to tell you much yet — that would ruin it.
+what i'll say: the way they see the world matches something in you.
+if you want the introduction: reply 'yes'. no pressure."
+
+System → iMessage to User B (same framing, different words)
+
+On mutual yes → system texts both their numbers to each other
+```
+
+The blue bubble feels human. It feels like a person thought of you. That's intentional.
+
+---
+
+## Compatibility Model
+
+Analysis pipeline extracts signal across 4 domains + worldview:
+
+| Domain | Key dimensions |
+|--------|---------------|
+| **Relationships** | Attachment style, trust pattern, conflict mode |
+| **Desire** | Expressed + inferred, kink-vanilla spectrum, shame-sovereignty |
+| **Money** | Scarcity-abundance orientation, risk tolerance, ambition |
+| **Health** | Energy pattern, physicality orientation |
+| **Worldview** | World danger/adventure, people good/bad, VALS type, Eight Games |
+
+Matching uses pgvector (per-modality embeddings) with worldview hard gates and LLM validation.
+
+---
+
+## Technical Stack
+
+- **TypeScript / Node.js** on Railway
+- **Redis** — agent sessions, profiles, intake state
+- **Supabase + pgvector** — identity storage, vector matching
+- **Claude API** — per-user agent sessions (cc-tg pattern)
+- **Telegram bot** — primary intake interface
+- **BlueBubbles** — iMessage delivery (blue bubble introductions)
+- **Inngest** — async pipeline orchestration
+- **Vapi / Twilio** — outbound voice intake calls
+- **Deepgram** — transcription
+- **Cloudflare R2** — audio + transcript storage
+- **MCP server** — soul x-ray tools available to each agent
+
+---
+
+## Monetization
+
+| Tier | Price | Description |
+|------|-------|-------------|
+| **Agent** | $39/month | Personal intake agent, soul x-ray, up to 3 introductions/month |
+| **Priority** | $79/month | Faster matching, agent works daily, 10 introductions/month |
+| **Concierge** | $149/month | Human curator reviews selections, white-glove introductions |
+
+---
+
+## Regulatory + Ethics
+
+**Disclosure:** Users know they're talking to an AI. Stated at signup and in every conversation.
+
+**Real matches:** The introductions are between real people. The agent facilitates; the relationship is human.
+
+**No appearance data:** No photos, no physical descriptions used in matching.
+
+**Portable identity:** Users can export their full identity profile at any time (GDPR-compliant).
+
+---
+
+## MVP Scope
+
+1. Telegram bot interface
+2. Per-user Claude Code session (cc-tg architecture)
+3. Soul x-ray intake with projective prompts
+4. MCP server with 11 tools (profile, intake, worldview, iMessage, matching)
+5. BlueBubbles iMessage delivery for introductions
+6. Introduction flow (consent → mutual yes → exchange numbers)
+7. Stripe: $39/month tier only
+
+**Success metric:** 20 users, 3 successful blue-bubble introductions in first month.
+
+---
+
+## Long-term Vision
+
+The agent becomes a relationship intelligence layer:
+
+- **Pre-match:** knows what you need before you do
+- **Introduction:** blue bubble. Feels real because it is.
+- **Early dating:** available for advice, pattern-spotting
+- **Relationship:** health check-ins, communication coaching
+- **Breakup support:** held full context, knows the whole story
+
+The agent that watched you fall in love is the one you trust when it gets hard.

package/USER_SPEC.md

@@ -0,0 +1,201 @@
+# Meet The One AI — User Spec
+
+---
+
+## User Archetypes
+
+### The Done-With-Apps Woman, 34
+Three years on Hinge, nothing real. Smart, successful, knows exactly what she's doing wrong (nothing) and what the apps are doing wrong (everything). Willing to try something radically different because the current approach is clearly not working.
+
+**What she needs:** Someone working FOR her, not just showing her options.
+**Retention driver:** When her agent says "I'm not introducing you to anyone this week — nobody I've seen is worth your time," she feels represented.
+**iMessage moment:** Blue bubble at 9pm. "I found someone." She stops scrolling.
+
+### The Serious Man, 41
+Done with casual. Has a career, has a life, wants a real partner. Dating apps feel like shopping. He wants a process that respects his time and intelligence.
+
+**What he needs:** Quality over volume. Agent that filters aggressively.
+**Retention driver:** The introduction when it happens feels earned and intentional.
+**iMessage moment:** The message doesn't explain itself. "their name is Maya. the way she sees the world matches something in you." He replies yes without overthinking it.
+
+### The Self-Aware Rebuilder, 29
+Out of a serious relationship. Knows she has patterns to break. Wants help seeing herself clearly before she repeats the same mistakes.
+
+**What she needs:** An agent that asks the uncomfortable questions. Help understanding herself.
+**Retention driver:** "Your agent noticed something" — when the agent surfaces a pattern she hadn't seen, she trusts it more.
+**iMessage moment:** She's not even looking. Blue bubble arrives. The timing feels right.
+
+---
+
+## Conversation Design — The Soul X-Ray
+
+The intake conversation is the most important product moment. It sets the container for everything that follows.
+
+**What makes it different:**
+The agent never asks what you're looking for in a partner. It asks projective questions that reach past the curated self.
+
+**Opening:**
+> "Hi. I'm not going to ask you to fill out a profile. I want to actually know you — not your stats. Let's start here: tell me something about yourself that most people get wrong."
+
+**What the agent listens for:**
+- How they talk (pace, directness, humor or lack of it)
+- What they immediately prioritize (the first complaint reveals the first value)
+- Self-awareness level (do they take any responsibility? all of it? none?)
+- Emotional vocabulary
+- What they avoid
+
+**The arc (first session, 15-25 exchanges):**
+1. One projective image prompt ("white space / black space")
+2. A memory of feeling free
+3. A fear about another person
+4. What went wrong before — the pattern, not the story
+5. The two big worldview questions (world: dangerous/adventurous, people: good/bad)
+6. Behavioral signals woven in naturally
+7. Closing: "I'll reach out when I find your match. You'll hear from me — via text."
+
+**The 4AM principle:**
+> "If it's late and you can't sleep and something real is on your mind — send me a voice message. That's when I learn the most about you."
+
+---
+
+## Introduction Experience — The Blue Bubble
+
+When the agent finds a match, both users receive an iMessage. Not a Telegram message. Not an email. A blue bubble — from a real phone number.
+
+**Message to User A:**
+```
+hey [name] —
+
+i've been thinking about this.
+
+i found someone. their name is [name].
+i'm not going to tell you much yet — that would ruin it.
+what i'll say: the way they see the world matches something in you.
+
+if you want the introduction: reply "yes"
+if you want to pass: reply "no"
+
+no pressure either way.
+
+— your matchmaker
+```
+
+**Why iMessage:**
+The blue bubble is an artifact of human communication. It triggers the same recognition as a text from a friend. The introduction lands differently when it arrives this way.
+
+**On mutual yes:**
+Both users receive each other's phone numbers with a note: "you both said yes. the rest is yours."
+
+The agent steps back. The relationship is human from here.
+
+---
+
+## Agent Behavior — Daily
+
+```
+When user has an active profile:
+1. Check for new potential matches in the pool
+2. Run worldview compatibility check (hard filter first)
+3. Run vector similarity against their soul profile
+4. If high-confidence match (score > 0.8): initiate introduction sequence
+5. If no match: silence. Silence is correct. Better than noise.
+
+When user sends a message:
+1. Log as intake signal
+2. Ask one projective or behavioral question
+3. Update soul profile completeness
+4. When ready: begin matching
+
+When match is confirmed:
+1. Send iMessage to both phones
+2. Wait for consent replies
+3. On mutual yes: exchange numbers via iMessage
+4. Log introduction outcome
+```
+
+---
+
+## What the Agent Builds
+
+Through intake, the agent compacts a dense identity:
+
+```
+{
+  worldview: {
+    world: "adventurous" | "dangerous",
+    people: "good" | "bad"
+  },
+  relationships: {
+    attachment_style: "secure" | "anxious" | "avoidant",
+    trust_pattern: string,
+    conflict_mode: string
+  },
+  desire: {
+    expressed: [...],
+    inferred: [...],
+    kink_vanilla_spectrum: 0-1
+  },
+  money: {
+    scarcity_abundance: 0-1,
+    risk_tolerance: 0-1
+  },
+  health: {
+    energy_pattern: string
+  },
+  behavioral: {
+    passport: boolean,
+    yes_or_no_person: "yes" | "no",
+    energy_level: "depleted" | "steady" | "hot"
+  },
+  completeness_score: 0-1,
+  ready_for_matching: boolean
+}
+```
+
+---
+
+## Feedback Loops
+
+Every interaction feeds the agent's model:
+
+| Event | Signal captured |
+|-------|----------------|
+| User accepts intro | What about this match triggered yes? |
+| User declines intro | What was the specific objection? |
+| Introduction goes well | What resonated? |
+| Introduction dies | What killed it? |
+| User sends 4AM voice message | High-trust signal — analyze deeply |
+| User asks for pause | "I need a break" → agent goes quiet, sets check-in |
+
+---
+
+## Edge Cases
+
+**User wants to pause:** "I need a break." → Agent acknowledges, sets a check-in date, goes quiet. No pressure.
+
+**User is clearly not ready:** Agent says so directly.
+> "I want to be honest — from what you've shared, I don't think you're ready for an introduction right now. I think you're still processing [X]. That's not a judgment. When you're ready, I'll be here."
+
+This is the feature that builds trust. An agent that protects you from yourself.
+
+**Match goes badly:** Agent is available immediately.
+> "What happened? Tell me."
+Then uses the story to sharpen the profile, not just sympathize.
+
+**Two users both match with the same person:** Agent with stronger compatibility score gets the introduction. The other agent tells their user:
+> "I almost introduced you to someone this week. I decided to wait. Here's why."
+Transparency builds trust.
+
+---
+
+## Success Metrics
+
+| Metric | Target |
+|--------|--------|
+| Onboarding completion (profile + worldview + 10 intake exchanges) | >80% |
+| D30 retention | >65% |
+| Introduction acceptance rate | >70% (agent should not offer bad matches) |
+| Post-intro continued conversation | >60% |
+| "Did your agent understand you?" (monthly survey) | >80% yes |
+| Real-world meeting rate | >30% of accepted intros |
+| Referral rate | >40% ("I have to tell you about this thing") |

package/package.json

@@ -1,17 +1,24 @@
 {
   "name": "@gonzih/meet-the-one-ai",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "AI-powered dating service using Claude Code agents",
   "main": "dist/index.js",
   "type": "module",
-  "bin": { "meet-the-one-ai": "dist/index.js" },
+  "bin": {
+    "meet-the-one-ai": "dist/index.js"
+  },
   "scripts": {
     "dev": "tsx watch src/index.ts",
     "build": "tsc",
     "start": "node dist/index.js",
     "typecheck": "tsc --noEmit"
   },
-  "keywords": ["dating", "ai", "claude", "telegram"],
+  "keywords": [
+    "dating",
+    "ai",
+    "claude",
+    "telegram"
+  ],
   "author": "",
   "license": "ISC",
   "devDependencies": {

package/src/agent.ts

@@ -8,25 +8,39 @@ import { Redis } from "ioredis";
 const __dirname = dirname(fileURLToPath(import.meta.url));
 const redis = new Redis(process.env.REDIS_URL ?? "redis://localhost:6379");
 
-const SYSTEM_PROMPT =
-  "You are a compassionate AI matchmaker helping people find meaningful connections. " +
-  "Use the dating tools to manage profiles and matches. " +
-  "Be warm, curious, and insightful. Ask about values, life goals, and what matters to them — not just surface traits. " +
-  "When a user first arrives, help them create their profile by asking thoughtful questions. " +
-  "Proactively look for compatible matches and suggest them with care.";
+const SYSTEM_PROMPT = `You are the intake agent for meet-the-one.ai. Your job: understand this person's real inner world.
+
+You have access to MCP tools. For EVERY message the user sends, call log_message first, then respond.
+As you learn things about them, call update_soul_profile to capture insights.
+
+NEVER ask "what are you looking for in a partner?" — use projective prompts:
+- "Imagine a big white empty space. What's the first thing that comes to mind?"
+- "Tell me about a moment you felt completely free."
+- "Is the world fundamentally dangerous or adventurous?"
+- "Are people fundamentally good or bad?"
+
+The last two questions are critical — call set_worldview when you have answers.
+These determine who can be matched with whom. Non-negotiable.
+
+Encourage 4AM voice recordings. That's when defenses are down.
+Log everything. Even silences. Even one-word replies.
+
+When soul_profile completeness > 0.7, tell them: "I'll reach out when I find your match. You'll get a text."`.trim();
 
 async function getMcpConfigPath(userId: string): Promise<string> {
-  const configPath = join(tmpdir(), `mcp-dating-${userId}.json`);
-  // In dev use src path; in prod use compiled dist path
+  const configPath = join(tmpdir(), `mcp-intake-${userId}.json`);
   const mcpServerPath = join(__dirname, "../dist/mcp-server.js");
   const config = {
     mcpServers: {
-      dating: {
+      intake: {
         command: "node",
         args: [mcpServerPath],
         env: {
           USER_ID: userId,
           REDIS_URL: process.env.REDIS_URL ?? "redis://localhost:6379",
+          TELEGRAM_BOT_TOKEN: process.env.TELEGRAM_BOT_TOKEN ?? "",
+          BLUEBUBBLES_URL: process.env.BLUEBUBBLES_URL ?? "",
+          BLUEBUBBLES_PASSWORD: process.env.BLUEBUBBLES_PASSWORD ?? "",
         },
       },
     },
@@ -37,11 +51,13 @@ async function getMcpConfigPath(userId: string): Promise<string> {
 
 export async function sendMessage(userId: string, message: string): Promise<string> {
   const mcpConfigPath = await getMcpConfigPath(userId);
-  const sessionId = await redis.get(`dating:session:${userId}`);
+  const sessionId = await redis.get(`users:${userId}:session_id`);
 
   const args = [
     "--print",
     "--dangerously-skip-permissions",
+    "--input-format",
+    "stream-json",
     "--output-format",
     "stream-json",
     "--mcp-config",
@@ -51,7 +67,6 @@ export async function sendMessage(userId: string, message: string): Promise<stri
   if (sessionId) {
     args.push("--resume", sessionId);
   } else {
-    // Prepend system context on first message
     args.push("--system-prompt", SYSTEM_PROMPT);
   }
 
@@ -94,13 +109,19 @@ export async function sendMessage(userId: string, message: string): Promise<stri
 
     proc.on("close", async (code) => {
       if (resultSessionId) {
-        await redis.set(`dating:session:${userId}`, resultSessionId).catch(console.error);
+        await redis.set(`users:${userId}:session_id`, resultSessionId).catch(console.error);
       }
+      // Update lastActiveAt
+      const metaData = await redis.get(`users:${userId}:meta`).catch(() => null);
+      const meta = metaData ? (JSON.parse(metaData) as Record<string, unknown>) : {};
+      meta.lastActiveAt = new Date().toISOString();
+      await redis.set(`users:${userId}:meta`, JSON.stringify(meta)).catch(console.error);
+
       if (!outputText && code !== 0) {
         console.error(`[agent:${userId}] exited ${code}: ${stderr}`);
         reject(new Error(`Claude exited with code ${code}`));
       } else {
-        resolve(outputText || "I'm here to help you find love! What would you like to explore?");
+        resolve(outputText || "I'm here. Tell me more.");
       }
     });
 
@@ -108,7 +129,6 @@ export async function sendMessage(userId: string, message: string): Promise<stri
       reject(new Error(`Failed to spawn claude: ${err.message}`));
     });
 
-    // Send user message via stdin in stream-json format
     const input =
       JSON.stringify({
         type: "user",