Architecture
Connects to Tableau, not around it
DRISHTI never connects directly to the databases behind a Tableau workbook. Data may only arrive through an authorized Tableau interface, with the user's own permissions. RLS BEHAVIOR — NOT YET VALIDATED.
- UserIMPLEMENTED
- DRISHTI ChatIMPLEMENTED
- Query OrchestratorIMPLEMENTED
- Semantic RouterIMPLEMENTED
- Query PlannerIMPLEMENTED
- Tableau GatewayABSTRACTION ONLY
- Supported Tableau InterfaceNOT YET IMPLEMENTED
- TableauINTEGRATION REQUIRED
- Authorized Workbook / ViewNOT YET VALIDATED
- Authorized Returned DataDEMO SYNTHETIC ONLY
- Deterministic AnalyticsIMPLEMENTED
- ValidationIMPLEMENTED
- AI ExplanationNOT CONFIGURED — deterministic template
- Evidence-backed ResponseIMPLEMENTED
Supporting components
Every field carries provenance: TABLEAU DISCOVERED, USER CONFIGURED or DEMO SYNTHETIC. AI output never becomes catalog fact.
Synonyms per catalog field drive routing; no separate glossary editor yet.
Query traces are shown per answer but not persisted.
Interface exists; no provider is connected. Credentials are never sent to an AI provider.
All Tableau capabilities are NOT CONFIGURED or NOT YET VALIDATED.
Join safety
Cross-source relationships are VALIDATED, USER CONFIRMED, INFERRED — VALIDATION REQUIRED, INCOMPATIBLE or UNKNOWN. Similar field names never create a join; inferred relationships cap confidence at LOW.
Numbers
Every figure is labelled TABLEAU SOURCE, CALCULATED, USER PROVIDED, DEMO SYNTHETIC or UNKNOWN. AI is never a number source.