What's LIVE Today
FLY Sales Bot v2 is deployed and operational on Railway. All P0/P1 features from the original spec are complete.
Conversation Engine
LIVE4-node LangGraph StateGraph: classify (Haiku) → retrieve (4-layer hybrid) → generate (Sonnet 4.5 streaming) → validate (Haiku anti-hallucination)
Knowledge Base
LIVE300 documents, 1,010 chunks, 71,819 graph edges. Semantic (50%) + Graph (35%) + Keyword (15%) retrieval with RRF fusion.
Chat Interface
LIVESSE streaming, markdown rendering, Mermaid diagrams, 4 artifact types (concept, testimonial, CTA, progress cards).
Feedback + Admin
LIVEThumbs up/down with comments, admin dashboard (filter, tag, status, notes), sources panel slide-out with graph edges.
What LaMonte Told Us
Four critical feedback items that define the Phase 0→1 evolution.
"Not quite in the right way"
Bot uses generic AI comfort language instead of LaMonte's intentional NLP delivery style. Needs Socratic method — 5 questions for every 1 principle.
"Kill the grooming language"
No "I hear you," no "That's completely valid." Questions should be one-liners without explanation. Ask → listen → ask again → THEN teach.
"Bot goes too deep"
Pulls program-level content (Day 30, six human needs) for prospect questions. Sales bot should only access sales-tier content.
"Guide the session"
Structured 3-module guided experience, not open-ended chatbot. Bot leads, user follows. Module 1 → Module 2 → Module 3 → CTA.
Confirmed Decisions
| Decision | Detail |
|---|---|
| 3-module scope | (1) Foundational principles → left/right side, (2) Clarity session exercise, (3) Neural addictions + internal vs external |
| Socratic method | 5:1 question-to-principle ratio. Short questions, long user responses, deeper drilling, then integrated insight delivery |
| Clarity session = key artifact | Left/right side form as interactive worksheet — the core differentiator |
| 20-min minimum | Set expectations upfront; possibly limit free sessions to 30 minutes |
| Content tiering | Learn to FLY = sales scope; 30 modules = post-sales; facilitator training = excluded |
| Video clips desired | Short clips of LaMonte teaching concepts, rendered as artifacts |
| Email campaigns | Personalized follow-up using interaction data for non-converters |
"Make It Sound Like LaMonte"
Before the follow-up call, the bot should FEEL different — Socratic, intentional, sales-scoped. Zero new features, maximum persona impact.
CP-1: Persona Overhaul
Rewrite prompts.py — prompt-only change, zero code. Replace warmth-first persona with Socratic-first identity.
- Rewrite PERSONA: "You are a questioner. You probe. You listen. You ask again."
- Promote V3_INQUISITION to PRIMARY behavior (5:1 ratio explicit)
- Add VOICE_ANTI_PATTERNS: banned comfort phrases with replacements
- Reorder Response Guidelines: "Ask before you teach" = #1
- Test 10 common prospect inputs, verify Socratic pattern
- Deploy to Railway, notify LaMonte to test
CP-3: Vault Enrichment
Populate enrichment folders (concepts, exercises, patterns, voice, progression) with tier-tagged reference cards extracted from 300 source files. Each file tagged tier: sales|program|facilitator for retrieval filtering.
CP-2: Content Tier Filtering
Add tier metadata filter to retrieval.py. Default queries filter to tier: sales only. Phase 1 modules can relax filter for deeper content when user is ready.
Decision: Metadata filter (Option A) — WHERE metadata->>'tier' = 'sales' clause on semantic retriever SQL. Hard boundary, not re-rank boost.
CP-4: Re-Ingest with Tier Tags
Propagate tier tags from enrichment → source frontmatter → chunk metadata → production database. Verify with SQL counts and end-to-end test query.
✓ Bot asks 3-5 questions before teaching any principle
✓ Zero "I hear you" / "That's completely valid" / "Great question!" responses
✓ "What is FLY?" returns sales-tier content only
✓ LaMonte says "that sounds more like me"
Decisions Pending from LaMonte
4 items blocked on LaMonte's input. Mitigations in place for all — none are hard blockers to Phase 0.
FLY_EVENT_DATE and FLY_EVENT_URL environment variables on Railway."Guided Experience MVP"
Transform from open-ended chatbot to structured 3-module guided journey with form artifacts, session management, and user profiles.
DP-1: 3-Module StateGraph Architecture
Restructure the linear 4-node graph into a module-aware routed architecture. Each module has its own system prompt variation, retrieval filter, and exit conditions.
| Module | Scope | Style | Exit Condition |
|---|---|---|---|
| 1: Foundations | NAAP principles, free/confined state, towards/away-from | Socratic questioning | User demonstrates concept understanding |
| 2: Clarity Session | Left/right side exercise | Guided interview + form artifact | User completes left/right form |
| 3: Neural Addictions | Why patterns repeat, internal vs external focus | Integrated insight + CTA | Readiness signals → book session |
DP-2: Clarity Session Form Artifact
Interactive two-column form artifact embedded in the chat. Left column = "Away from" (fears, patterns, pain). Right column = "Towards" (goals, aspirations). Submits to POST /api/profile/clarity-session, saved to user_profiles table, referenced in Module 3 for personalized insight.
DP-3: Session Structure
Welcome flow with 3-module overview. 20-min commitment framing. Progress indicators via progress_card artifacts at transitions. Optional 30-min session limit.
DP-4: User Profile Persistence
Persist Socratic responses, engagement depth, readiness signals beyond clarity form. Feeds email campaigns (DP-7). New user_profiles PostgreSQL table.
DP-5: Video Clip Artifacts
New video_card artifact type. Start with YouTube embeds mapped to concept timestamps. LaMonte's face + voice builds trust faster than text.
DP-6: Dashboard UI Redesign
Three-pane layout: modules (left), chat (center), history/artifacts (right). Deferred to late Phase 1 — current UI is functionally sufficient.
DP-7: Email Campaigns
Personalized follow-up emails using interaction data. Trigger: X hours after incomplete session. Requires email service (SendGrid/Resend) + DP-4 profile data.
Dependency Chain
How Phase 0 gates unlock Phase 1 work.
Phase Transition Gate: Phase 0 → Phase 1
- Bot asks 3-5 questions before any principle (Socratic verification)
- Zero AI comfort phrases in responses (anti-pattern verification)
- "What is FLY?" returns sales-tier content only (tier filter verification)
- LaMonte has tested and provided feedback (voice calibration)
- All enrichment files have tier tags (content inventory complete)
Risk Register
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| Persona overhaul makes bot too terse / robotic | Medium | High | Test with feedback system before follow-up call. Keep V5_SALES_VOICE as warmth anchor. Iterate rapidly. |
| Tier filtering too aggressive — legitimate questions go unanswered | Medium | Medium | Start with tier filter + fallback: if no sales-tier results, expand to program-tier with disclaimer. Monitor via sources panel. |
| 3-module graph breaks existing functionality | Low | High | Feature branch. Test suite (1,693 lines). Keep linear flow as fallback path. |
| Clarity session form UX too complex | Medium | Medium | Start with plain text inputs, not fancy interactive form. Iterate on feedback. |
| LaMonte doesn't test between calls | High | Medium | Send 5 specific test prompts + direct link. Set up Railway notification on feedback submission. |
| Module transition detection unreliable | Medium | Medium | Start with explicit transitions ("Ready for the next step?") rather than implicit detection. |
Content Tier Inventory
What the sales bot SHOULD access vs what it should NOT.
Sales Tier (75 files, ~55K words)
Three NAAP Principles · Free/Confined State · Neural Addiction (overview) · Towards vs Away-From · Three Stages of Transformation · Neuroplasticity · The Big Lie · Testimonials · Differentiation list · Social proof stats · Clarity session exercise · FLY Micro Experience
Program Tier (195 files, ~420K words) — EXCLUDE
Six Human Needs (Days 19-26) · Belief System Audit · RAS · Morning Routine · Evening Journal · Pattern Worksheet · 30-day progression · Story Rewriting · Observation exercises