ishaq101 commited on
Commit
8dcc782
Β·
2 Parent(s): 19bd03735d3523

Merge branch 'main' of https://huggingface.co/spaces/DataEyond/Agentic-Service-Data-Eyond-Catalog

Browse files
Files changed (2) hide show
  1. ARCHITECTURE.md +10 -0
  2. REPO_CONTEXT.md +20 -0
ARCHITECTURE.md CHANGED
@@ -5,6 +5,16 @@
5
 
6
  ---
7
 
 
 
 
 
 
 
 
 
 
 
8
  ## TL;DR
9
 
10
  A catalog-driven AI service for data analysis. Users upload documents and register databases or tabular files; they ask natural-language questions and get answers grounded in their data.
 
5
 
6
  ---
7
 
8
+ ## Product vision (north star)
9
+
10
+ Data Eyond is an *AI data scientist* for business analytics, structured around **CRISP-DM** (Business Understanding β†’ Data Understanding β†’ Data Preparation β†’ Modeling β†’ Evaluation β†’ Deployment). Targets executives doing self-serve deep-dives and data analysts/scientists offloading routine work.
11
+
12
+ Envisioned user flow: **interview agent** captures goal β†’ user connects data sources β†’ asks natural-language question β†’ CRISP-DM-structured analytical response, exportable as a **presentation** or **notebook-style report**.
13
+
14
+ The catalog-driven, IR-based architecture documented below is the *foundation*. The next architectural evolution is an agentic layer (analytical planner, per-stage CRISP-DM agents, evaluator, reporter) that consumes the existing IntentRouter β†’ QueryPlanner β†’ Executor β†’ ChatbotAgent spine as its tool layer. See `REPO_CONTEXT.md` β†’ *Roadmap β€” agentic evolution* for the target agent topology.
15
+
16
+ ---
17
+
18
  ## TL;DR
19
 
20
  A catalog-driven AI service for data analysis. Users upload documents and register databases or tabular files; they ask natural-language questions and get answers grounded in their data.
REPO_CONTEXT.md CHANGED
@@ -4,6 +4,26 @@ Orientation file for future Claude Code sessions. Cross-reference `ARCHITECTURE.
4
 
5
  ---
6
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
7
  ## TL;DR
8
 
9
  FastAPI multi-agent backend for data analysis. Users upload documents and register databases / tabular files; they ask natural-language questions and get answers grounded in their data, streamed via SSE.
 
4
 
5
  ---
6
 
7
+ ## Product vision β€” Data Eyond, your AI data scientist
8
+
9
+ Data Eyond is positioned as an *AI data scientist* that supports business analytics. It is built around the **CRISP-DM** framework (Business Understanding β†’ Data Understanding β†’ Data Preparation β†’ Modeling β†’ Evaluation β†’ Deployment) β€” the agent works through data problems the way a real analyst would, not as a one-shot Q&A bot.
10
+
11
+ **Target users:**
12
+ - **Executives** β€” deep-dive into their own data and extract insight to drive business decisions without needing a data team in the loop.
13
+ - **Data analysts / scientists** β€” offload routine analysis so they can focus on heavier work.
14
+
15
+ **Envisioned user flow:**
16
+ 1. **Discovery interview** β€” a short conversation with a Data Eyond *interview agent* that draws out goal, business context, and what the user is actually trying to learn (CRISP-DM Business Understanding).
17
+ 2. **Connect data** β€” DB connection or file upload (DB, CSV, XLSX, Parquet, documents).
18
+ 3. **Ask Data Eyond** β€” natural-language analytical question.
19
+ 4. **CRISP-DM-structured analytical response** β€” exportable as a **presentation deliverable** or a **notebook-style report**.
20
+
21
+ North star: less "chatbot over a database", more "junior data scientist that hands back a polished, decision-ready deliverable."
22
+
23
+ The current repo (Phase 2, below) is the *foundation* β€” IntentRouter β†’ QueryPlanner β†’ Executor β†’ ChatbotAgent gives us a reliable structured-query spine. The next evolution is the agentic layer that turns this into an end-to-end CRISP-DM workflow (see *Roadmap β€” agentic evolution* further down).
24
+
25
+ ---
26
+
27
  ## TL;DR
28
 
29
  FastAPI multi-agent backend for data analysis. Users upload documents and register databases / tabular files; they ask natural-language questions and get answers grounded in their data, streamed via SSE.