Framework Visual Diagram

A node-and-arrow map: read left to right, follow the numbered flows, and hover blocks for details.

Framework Map: NestJS + Powabase + Mem0 Admin/FE call NestJS. NestJS orchestrates data/RAG in Powabase, user memory in Mem0, and external integrations through Connectors/Extensions. 1. Entry Points 2. NestJS Framework API Reusable logic layer exposing stable APIs for Admin/FE. 3. Platform Services 4. Outputs Admin Console Upload source documents Review/edit atoms Test RAG / configure FE / Website Page context Chat messages Gen UI actions Lead/demo forms Project Config Taxonomy / page map Theme / prompts Auth / Workspace Resolve client, permissions, config Admin API Sources, atoms, approval, reindex Context Engine UTM, page, user behavior Case Router User intent -> processing flow Slot Engine Known facts / missing fields RAG Orchestrator Filter knowledge + citations User Memory Mem0 or internal fallback AI Guardrails Approved sources only Gen UI Engine Block spec + action schema Lead / Events Merge leads, tracking, handoff Notifications Slack, email, webhook Extension Layer Client-specific APIs/tools Powabase Postgres + custom tables Store sources/assets Primary knowledge base Chunk/vector/RAG Store leads/events/sessions Mem0 Known user facts Cross-session memory Preferences / pain points Connectors / Extensions Slack / Email / LINE HubSpot / Salesforce Custom tools: ROI, booking Admin Output Approved atoms RAG indexed Audit logged FE Output Answer + sources Gen UI blocks Updated slots Sales / Operations Lead created Slack sent CRM synced 1 Admin API 2 Runtime API 3 Load config 4 RAG / DB / Storage 5 Find/save memory 6 Tools / notifications 7 8 9 10 Response returns to FE/Admin through NestJS API How to read the numbers 1. Admin calls APIs to upload documents, edit atoms, approve, reindex, or configure notifications/extensions. 2. FE calls APIs when a user chats, clicks Gen UI, submits a form, or requests a demo. 3. NestJS loads client config: taxonomy, page map, prompt/rules, connector settings. 4. NestJS calls Powabase to store data, query RAG, fetch approved atoms/chunks, and save leads/events. 5. NestJS calls Mem0 to read/save long-term user memory such as industry, company size, and known pain points. 6. NestJS calls connectors/extensions for Slack, CRM, email, webhook, or custom tools like ROI/booking. 7-9. External services return results: indexing completed, answer has sources, lead synced, Slack sent. 10. NestJS assembles a stable response for FE/Admin: answer, Gen UI blocks, updated slots, audit/result.