DataMindDataMindDesign SystemUI/UX & Design System Documentation
DATAMIND SUITE / EXPERIENCE SPECIFICATION

Governed intelligence,
designed for decisions.

A product UX framework for natural-language analytics, safe query execution, explainable insight and accountable action.

23chapters2first-class languages1governed experience
01 / UX SPECIFICATION

Product & UX Overview

DataMind is a governed data-intelligence assistant. Natural language is the entry point; validation, permissions, provenance and user control shape every outcome.

01Natural language first
02Explainability
03User control
04Safe by default
05Permission awareness
06Validate before execution
07Explicit confirmation
08Visible provenance
09Facts ≠ interpretation
10Persian & English first
11Progressive disclosure
flowchart

Governed intelligence pipeline

Rendering diagram…
The model proposes; validation and controlled execution remain explicit product boundaries.
02 / UX SPECIFICATION

Personas

The experience adapts to analytical maturity and responsibility without fragmenting the product into separate tools.

Business User

Low–medium
Primary goals
Ask without SQL; understand charts; save dashboards
Important UX needs
Trust, plain language, Persian/English

Data Analyst

High
Primary goals
Generate and debug SQL; reuse metrics
Important UX needs
Review controls and technical detail

BI Admin

High
Primary goals
Permissions; approvals; usage governance
Important UX needs
Auditability and explicit confirmation

Data Engineer

High
Primary goals
Schema, glossary, metrics and approved joins
Important UX needs
Precise definitions and change ownership

System Admin

High
Primary goals
Deployment, models, security and monitoring
Important UX needs
Environment visibility without secret exposure
STAKEHOLDERS / ذی‌نفعان

Accountability beyond end users

Product / Engineering Team

Owns product scope, delivery and technical quality.

مالک محدوده محصول، تحویل و کیفیت فنی

Technomind AI Product Team

Primary internal sponsor and delivery stakeholder.

حامی داخلی و ذی‌نفع اصلی تحویل محصول

Client Data & BI Leadership

Owns data definitions, Metabase governance and rollout.

مالک تعاریف داده، حاکمیت Metabase و استقرار

Security & Compliance

Defines PII, external inference and direct-access policy.

تعریف‌کننده سیاست PII، پردازش بیرونی و دسترسی مستقیم

Pilot Users

Validate usefulness, clarity, latency and correction behavior.

اعتبارسنجی کاربردپذیری، وضوح، سرعت و اصلاح نتایج

journey

Business user - Ask and understand

Rendering diagram…
The clarification moment is intentionally lower-confidence; the UX must restore clarity before execution.
03 / UX SPECIFICATION

User Goals & Jobs

Design around the decision a person is trying to make - not around the model or connector doing the work.

Business User

I want to ask a business question and understand the answer without knowing SQL.

Data Analyst

I want DataMind to generate and validate a query so I can focus on analysis.

BI Admin

I want generated dashboards confirmed before they become shared assets.

Data Engineer

I want approved terminology and relationships to be used correctly.

System Admin

I want to control where models run and how data leaves the environment.

PRD v0.2 / US-01-US-14

Bilingual user-story catalogue

US-01P0Business User

Ask in Persian and preview a validated Metabase question without writing SQL.

پرسش فارسی و مشاهده پیش‌نمایش سؤال اعتبارسنجی‌شده Metabase بدون نوشتن SQL.

AcceptanceSchema retrieved · SQL validated · preview before save
US-02P0Business User

Use English or mixed Persian-English business terminology.

استفاده از واژگان انگلیسی یا ترکیبی فارسی–انگلیسی.

AcceptanceApproved glossary and schema mapping
US-03P0Data Analyst

Inspect and edit SQL before saving a Metabase question.

بررسی و ویرایش SQL پیش از ذخیره سؤال در Metabase.

AcceptanceSQL · explanation · confidence · tables · assumptions · validation
US-04P0BI Admin

Save generated content into a selected Metabase collection.

ذخیره محتوای تولیدشده در collection انتخابی Metabase.

AcceptanceCreated object link returned
US-05P1BI Admin

Create dashboards from a high-level request after confirmation.

ساخت داشبورد از درخواست سطح‌بالا پس از تأیید.

AcceptancePropose cards · validate each · confirm · create
US-06P0Data Engineer

Register metrics and synonyms used in provenance.

ثبت معیارها و مترادف‌هایی که در منشأ نتیجه نمایش داده می‌شوند.

AcceptanceSearchable, versioned glossary definitions
US-07P0System Admin

Choose local CPU, local GPU or external API inference.

انتخاب استنتاج CPU محلی، GPU محلی یا API بیرونی.

AcceptanceProvider switches without business-logic changes
US-08P0BI Admin

Audit prompts, SQL, models, latency and created objects.

ممیزی prompt، SQL، مدل، latency و objectهای ساخته‌شده.

AcceptanceComplete trace event per request
US-09P1Business User

Receive clarification when a request is ambiguous.

دریافت سؤال شفاف‌ساز هنگام ابهام درخواست.

AcceptanceTargeted choice instead of guessing
US-10P1Data Analyst

Review bounded correction when SQL fails.

بررسی اصلاح محدود هنگام شکست SQL.

AcceptanceMaximum 2 attempts · final diff visible
US-11P0BI Admin

Use DataMind Suite identity beyond the Metabase connector.

استفاده از هویت DataMind Suite فراتر از اتصال Metabase.

AcceptanceConsistent product naming
US-12P1Business User

Receive a direct insight through an approved read-only connection.

دریافت بینش مستقیم از اتصال فقط‌خواندنی تأییدشده.

AcceptanceSafe SQL · bounded table · summary · chart suggestion
US-13P1Data Analyst

Publish a reviewed direct insight to Metabase.

انتشار بینش مستقیم بازبینی‌شده در Metabase.

AcceptancePrompt, SQL, chart and metadata preserved
US-14P0Security / Admin

Govern Direct DB independently from Metabase.

حاکمیت مستقل Direct DB از Metabase.

AcceptanceEnable/disable · permissions · limits · PII · audit · approval
04 / UX SPECIFICATION

Information Architecture

Separate asking, reusable outcomes, organizational knowledge, governance and administration.

flowchart

Information Architecture

Rendering diagram…
This is the product content hierarchy, not the backend system architecture.
06 / UX SPECIFICATION

Core User Flows

Every flow preserves intent, validates generated work and introduces confirmation before consequential creation.

sequence

Core natural-language query

Rendering diagram…
Invalid SQL returns to bounded correction; only validated read-only SQL reaches execution.
flowchart

Dashboard creation flow

Rendering diagram…
Confirmation is an explicit gate before creating a consequential Metabase asset.
07 / UX SPECIFICATION

Natural Language Query UX

Persian, English and mixed-language prompts resolve into visible intent, assumptions, query and next actions.

نمودار فروش ماهانه استان تهران در ۱۲ ماه گذشته را بساز

Monthly sales · TehranValidated
IntentTrend analysisConfidence94%VisualizationLine chartConfirmationNot required
08 / UX SPECIFICATION

AI Interaction Model

Communicate progress and decision points without exposing chain of thought or infrastructure noise.

state

AI interaction state machine

Rendering diagram…
Clarification, correction, permission denial and unsafe blocking are first-class states - not generic errors.
IdleClear user-facing status
UnderstandingClear user-facing status
Retrieving contextClear user-facing status
Generating SQLClear user-facing status
Validating SQLClear user-facing status
ExecutingRunning approved query
Generating insightClear user-facing status
Waiting for confirmationClear user-facing status
CompletedClear user-facing status
Needs clarificationClear user-facing status
CorrectingClear user-facing status
FailedClear user-facing status
Permission deniedClear user-facing status
No dataClear user-facing status
09 / UX SPECIFICATION

Clarification & Ambiguity Handling

When multiple valid meanings exist, DataMind asks a targeted question instead of silently selecting one.

flowchart

Clarification flow

Rendering diagram…
The request فروش استان تهران is not executed until the ambiguous province dimension is resolved.
منظور شما از «استان» کدام است؟

دو تعریف معتبر در مدل داده پیدا شد. برای ادامه یکی را انتخاب کنید.

10 / UX SPECIFICATION

SQL Generation & Validation UX

SQL is collapsed by default, reviewable on demand and never executable when unsafe or unvalidated.

sequence

SQL generation and validation

Rendering diagram…
Only validated, safe, read-only SQL can execute. Invalid SQL gets at most two correction attempts; unsafe SQL is blocked.
Query generated and validatedRead-only · 2 tables · 1 approved metric
Validated
Blocked: INSERT · UPDATE · DELETE · DROP · ALTER · TRUNCATE · CREATE
11 / UX SPECIFICATION

Metabase Interaction UX

Metabase is a connector. DataMind owns intent, validation, confirmation and the cross-source experience.

sequence

Metabase interaction

Rendering diagram…
Dashboard and question creation require preview and confirmation before the connector creates an object.
DataMind for MetabaseApproved connector · Available
Connector
Question / CardPreview → confirm → createDashboardProposal → admin/user confirmationExisting objectOpen with permission-aware result linkFailureExplain permission or availability; offer retry
Metabase is a connector - not the boundary of the DataMind experience.
12 / UX SPECIFICATION

Dashboard Creation UX

Dashboard creation moves from proposal to review to explicit confirmation before an asset is created.

state

Dashboard lifecycle

Rendering diagram…
There is deliberately no Proposed → Created transition. Confirmation is mandatory.
PROPOSED DASHBOARD

Executive sales overview

4 cards · Metabase · Private until confirmed

Awaiting review
  1. 1Monthly RevenueValidated
  2. 2Revenue by ProvinceValidated
  3. 3Top ProductsValidated
  4. 4Monthly GrowthValidated
Creation occurs only after explicit confirmation.
13 / UX SPECIFICATION

Direct Database Insight UX

An optional, approved and policy-bound mode for bounded read-only database analysis.

sequence

Direct Database Insight · Optional

Rendering diagram…
Optional capability. The model never receives credentials and never executes SQL directly; the Data Access Gateway is the execution boundary.
Optional capability

Direct Database Insight

Approved · Read-only · Policy enforced
Data sourceFinance replicaBounded result · 500 rows max
ValidationPassedPermission-aware gateway
RecommendationBar chartCompare provinces

3 grounded insights Net revenue grew in 7 of 9 provinces. Tehran contributes the largest absolute increase.

14 / UX SPECIFICATION

Insight & Visualization UX

Computed facts and AI interpretation must remain visibly distinct.

FACT FROM DATA
+18.2%

Revenue increased compared with the previous period.

Computed from executed result
AI INTERPRETATION
Tehran-led

The increase appears concentrated in Tehran.

Interpretation · Review source details
Recommended visualizationLineBarAreaTableKPI
15 / UX SPECIFICATION

Provenance & Trust UX

Every important result can explain where it came from, how it was validated and when it was produced.

Why this result?

Evidence and execution details for the current answer.

Data sourceMetabase · Sales WarehouseTablesfact_sales, dim_regionFieldsnet_revenue, billing_provinceMetricNet Revenue · v2 · ApprovedValidationPassed · Read-onlyProduced2026-08-23 · 14:32
16 / UX SPECIFICATION

Feedback & Correction UX

Feedback should describe what was wrong and offer a direct recovery path.

Was this result useful?
17 / UX SPECIFICATION

States & System Behavior

Consistent state language prevents ambiguous loading, silent failure and premature success.

state

Assistant state machine

Rendering diagram…
state

Dashboard lifecycle

Rendering diagram…
ObjectAllowed states
AssistantIdleLoadingStreamingClarificationGeneratingValidatingExecutingCompletedNo DataPermission DeniedErrorRetryingWaiting for Confirmation
QueryDraftGeneratedValidatedRejectedCorrectingExecutedSaved
DashboardProposedReviewingAwaiting ConfirmationCreatingCreatedFailed
Direct DBDisabledAvailableRunningValidatedExecutedBlockedPublished
18 / UX SPECIFICATION

Error Handling

Errors explain the outcome, preserve useful context and present the safest next action.

SQL validation failed

The generated query did not pass validation. No query was executed.

Permission denied

This data is unavailable under your current permissions.

No matching data

The query completed successfully but returned no records.

Connector unavailable

Metabase is temporarily unavailable. Your request is preserved.

19 / UX SPECIFICATION

Permissions & Security UX

Security is visible enough to establish trust without overwhelming routine analysis.

Safe by default

Normal analysis is read-only, permission-aware and bounded before execution.

Read-only SQLAllowed tablesBlocked columns / PIIRow limitsQuery timeoutDirect DB enable / disableUser confirmationDashboard approvalAudit trail
20 / UX SPECIFICATION

Audit & Governance UX

Administrators can trace requests, retrieved context, validation, execution and resulting actions.

Audit log

Governed trace of analytical activity

TimeUserActionValidationObject
14:32sara@companyExecuted queryPassed-
14:28admin@companyCreated dashboardConfirmed#1842
14:04ali@companyBlocked SQLRejected-
Prompt · Model · Retrieved context · SQL · Execution metadata are available in row details.
21 / UX SPECIFICATION

Localization & RTL

Persian is a first-class product language; technical content keeps the direction it requires.

Net revenue in Tehran province

Review net revenue using the approved metric definition.

SELECT net_revenue FROM fact_sales;
RTL layoutVazirmatn typographyLTR SQL/codeMixed terminologyLocalized datesStable chart axes
22 / UX SPECIFICATION

Responsive Behavior

The experience preserves intent, review and confirmation across desktop, tablet and mobile.

Desktop

Persistent navigationSide-by-side reviewFull tables and chart context

Tablet

Collapsible navigationStacked detail panelsScrollable data tables

Mobile

Drawer navigationBottom-safe composerProgressive SQL and chart detail
23 / UX SPECIFICATION

UX Principles

A concise contract for every new workflow and component in DataMind.

  1. Ask, don’t guess.
  2. Validate before execution.
  3. Explain important decisions.
  4. Keep the user in control.
  5. Make data provenance visible.
  6. Separate facts from interpretation.
  7. Be safe by default.
  8. Respect permissions.
  9. Progressively disclose technical detail.
  10. Treat Persian and English as first-class.
  11. Confirm before consequential actions.
  12. Make failures actionable.