Resolve SCE - handover ecosystem

Everything orbits the working prototype. Ed clicks through it, dev team rebuilds from it, PRDs describe it. Solid green borders = live and accessible now. Dashed amber = gaps still to fill. Dashed red = migration items for dev team handover.

Central artifact - everything radiates from this

Lovable prototype (the working product)

The validated spec. Every screen a seller touches, every decision a broker makes, every credit spent. Ed sees this and clicks through it. Dev team rebuilds from this. PRDs describe what this does. Architecture diagrams map what's inside it. The prototype IS the product - everything else supports it.

Prototype: resolve-connect-engine.lovable.app
Lovable project: lovable.dev/projects/9a3e4e68...
Epic 2 COMPLETE (3 Apr 2026). 10 stories shipped: platform shell, 3-gate intake form, ABN verification (live ABR API), business name search, referral attribution, lead source tagging, account creation with real auth sessions, save and return, status timeline (9 states), submissions list, returning user router. Auth-first RLS architecture in place. Epic 3 (screening) starts next.
↓ built from / validated by
Code (GitHub)
resolve-design-system repo resolve-seller-connect-engine repo CLAUDE.md (agent instructions) Commit history + Layer 2 logs
Backend (Supabase)
Project live Auth (magic link, auth-first RLS) 4 tables (sellers, intake responses, business details, referral partners) 7 edge functions deployed Storage (files, audio - Epic 8)
Design system (single source of truth)
14 shadcn/ui components index.css tokens (Resolve theme) Storybook deployed .lovable/rules/ folder shadcn/studio Figma kit Code Connect mappings DS sync (Storybook ~15 components behind prototype)
Build tools + MCP servers
Lovable (UI scaffold) Claude Code (logic) Figma MCP (bidirectional) shadcn/studio Pro Context-7 MCP shadcn/ui + studio MCPs Figma use_figma (eval Week 4)
Documentation (Google Drive + project knowledge)
E1 Legal PRD (7)E2 Intake PRD (10 shipped)E3 Screening PRD (7) E4 Matching PRD (9)E5 Credit PRD (7)E6 Comms PRD (6) E12 Analytics PRD (12)E14 Emails PRD (5) Operational system (living)Tech stack registry Coverage mapCopy guidelines AI opportunity mapProduction build v3.2 Story build playbookOperational playbook
Project management
Trello (17 lists, 139 cards) Gantt v8 (deployed) Wireframes (18 views, deployed) Engine architecture v9 (deployed) AI opportunity map (deployed) Handover ecosystem (this doc, deployed) Ed assigned to action cards PM team owns E12
External services
ABR API (ABN verification - live) SendGrid via Twilio (email - awaiting credentials) Twilio Voice (masked relay) DocuSign (eSign) Stripe (credits + commission) Mixpanel (analytics) Anthropic API (TL;DR, scoring) Retell AI (voice screening)

Migration: Lovable environment to dev team

Lovable holds context that doesn't push to GitHub automatically. When the dev team takes ownership, these need to transfer to their working environment. This is the gap between "prototype works" and "dev team can rebuild from it."

.lovable/rules/ folder (component + pattern specs) Lovable Knowledge base entries (project context pasted per session) AI agent configurations (grounding rules, system prompts, what context gets injected) Lovable project settings (DS connection, GitHub sync config, workspace config) Prompt patterns that worked (what to paste, what order, what to avoid) Build session logs (Layer 2 on Trello cards - decisions made during build) Prototype env vars (Supabase keys, API tokens, feature flags) shadcn/studio Pro license (transfer or share credentials) Claude project knowledge files (PRDs, guidelines, architecture context)

GitHub captures code. Supabase captures data. But the AI tooling context - the rules, the grounding, the patterns that make Lovable and Claude Code produce correct output - lives outside both. This needs a dedicated migration doc written after the prototype is proven.

↓ dev team receives all of the above, plus
Dev team receives
Working prototype to click through Storybook URL (component catalog) GitHub repos (DS + prototype) Supabase project (schema + edge functions + data) Handoff briefs per epic (Layer 3 on Trello) Architecture diagrams Test scenarios per story Tech debt inventory + rebuild guidance Prototype vs production gap tables Lovable migration pack (rules, agents, patterns, knowledge) Layer 3 handoff briefs (written after stories ship) Lovable migration doc (written after prototype proven)

Live links (available now)

Prototype (Lovable deployed app) Lovable project dashboard Trello board Storybook (component catalog) Wireframes (18 views) Gantt v8 Engine architecture v9 AI opportunity map Handover ecosystem (this doc) GitHub - design system repo GitHub - prototype repo Supabase project Figma file Google Drive - operational docs
Last updated 6 April 2026. Update this doc before every meeting with Ed. The prototype URL is the front door - everything else explains what's behind it. Epic 2 is complete and clickable. Epic 3 (screening) is the next build cycle. The migration section gets its own detailed doc after the prototype is proven and before dev team starts rebuilding.