How debjoy26/text_ai_complete_product_doc works
This repository is a documentation-only product hub, not an implementation. Its documented principal workflow is a website visitor using the embeddable widget and visitor API, backed by tenant data and services. It also describes client administration and a separate, proposed provider-control experience. The graph reflects the README’s documented topology; component-level behavior and implementation paths are not available here, so subsystem nodes point to the relevant architecture or requirements documents.
Main entry points: PRODUCT_REQUIREMENTS.md Provider-admin experience · SYSTEM_ARCHITECTURE.md Visitor API · DATA_AND_API_CONTRACTS.md Approved RPCs
Components 20
Visitor service
- Static widget
SYSTEM_ARCHITECTURE.md - Visitor API
SYSTEM_ARCHITECTURE.md - Tenant database
SYSTEM_ARCHITECTURE.md - Vector search
SYSTEM_ARCHITECTURE.md - Private document storage
SYSTEM_ARCHITECTURE.md - Worker
SYSTEM_ARCHITECTURE.md
Client administration
- Client admin panel
PRODUCT_REQUIREMENTS.md - Supabase Auth
SYSTEM_ARCHITECTURE.md - RLS-protected reads
SYSTEM_ARCHITECTURE.md - Approved RPCs
DATA_AND_API_CONTRACTS.md - Supabase Storage
SYSTEM_ARCHITECTURE.md
Provider control plane
- Provider-admin experience
PRODUCT_REQUIREMENTS.md - Provider identity
SYSTEM_ARCHITECTURE.md - Control API
SYSTEM_ARCHITECTURE.md - Client registry
SYSTEM_ARCHITECTURE.md - Audit store
SYSTEM_ARCHITECTURE.md - Scoped tenant operations
SYSTEM_ARCHITECTURE.md
Other components
- Client website
- Client administrators
- Provider staff
Connections 17
- Client website → Static widget: embeds
README.md - Static widget → Visitor API: calls
README.md - Visitor API → Tenant database: uses
README.md - Visitor API → Vector search: uses
README.md - Visitor API → Private document storage: uses
README.md - Visitor API → Worker: uses
README.md - Client administrators → Client admin panel: uses
README.md - Client admin panel → Supabase Auth: uses
README.md - Client admin panel → RLS-protected reads: uses
README.md - Client admin panel → Approved RPCs: uses
README.md - Client admin panel → Supabase Storage: uses
README.md - Provider staff → Provider-admin experience: uses
README.md - Provider-admin experience → Provider identity: uses
README.md - Provider-admin experience → Control API: uses
README.md - Provider-admin experience → Client registry: uses
README.md - Provider-admin experience → Audit store: uses
README.md - Provider-admin experience → Scoped tenant operations: requests
README.md