Responsive UI component presenting consolidation details with adaptive layouts.

UI component for reviewing proposed data consolidations with visual cues.

The Frontend catalog dashboard is planned to be implemented as a SvelteKit frontend page for user interaction. FileAnalyzer produces data catalogs used in the extraction planning process. The data catalog generation process depends on the upload directory where user files are stored.

Integration involves modifying backend/app/main.py to register discovery API routes. The backend/app/main.py file starts the FastAPI app that exposes the API Layer.

Direct SQL is an option in the Agent Selector Dropdown for performing raw structured queries. Agent Selector directs queries to Direct SQL agent

Documentation detailing the multi-stage discovery process, backend services, UI components, and integration steps for the data discovery feature.

The DiscoveryFlow page uses Frontend UI components as part of the Data Discovery user experience. The DiscoveryFlow component is intended to be added and used in the /projects/[id]/analyze page file. The DiscoveryFlow component is intended to be added and used in the /projects/[id]/analyze page file. DiscoveryFlow component was integrated into the frontend analysis page to enable discovery UI. DiscoveryFlow depends on the Discovery API router for backend data and functionality. DiscoveryFlow is a UI component part of the Data Discovery system. DataLens system includes the DiscoveryFlow UI component for data discovery and consolidation. The DiscoveryFlow component is implemented using the Svelte framework. The DiscoveryFlow component uses Tailwind CSS for styling and responsive design. The DiscoveryFlow component is built with the shadcn stack, enabling modern UI features like gradients and animations. The Data Discovery Feature includes the DiscoveryFlow UI component used in analysis page for user interaction. Integration requires adding the DiscoveryFlow component to the analysis page for front-end functionality. Integration requires adding the DiscoveryFlow component to the analysis page for front-end functionality.

DiscoveryFlow Svelte component is part of the Data Discovery feature for guided data exploration. The Data Discovery feature includes the DiscoveryFlow Svelte component for guided data exploration.

A responsive UI component displaying loading state during data discovery processes.

The DataLens Platform utilizes DS-STAR extractors to transform catalog elements into structured data. The DS-STAR extractors are invoked via DS-STAR agents subprocess integration for extraction tasks.

DS-STAR queries use DS-STAR reasoning capabilities that leverage the rich metadata and embeddings from the Docling extraction system. The DOCX extractor produces semantic chunks with rich metadata including hierarchy and provenance to support DS-STAR queries for document reasoning. The PPTX extractor provides slide-based semantic chunks with detailed metadata including slide layout and image counts that DS-STAR queries utilize for document analysis.

The DataLens Platform uses the DS-STAR sql_agent to generate SQL queries from natural language questions.

DuckDBService manages data storage and querying using DuckDB as the database. QuestionRouter uses DuckDBService to execute and fetch results from SQL queries as part of structured query execution. QuestionRouter uses DuckDBService to execute and fetch results from SQL queries as part of structured query execution. DuckDBService and PgDataService are separate services managing database queries for different systems. ExportService uses DuckDBService to export query results in various formats. PgDataService and DuckDBService manage SQL database queries for PostgreSQL and DuckDB respectively. DuckDBService uses the DuckDB file as physical storage for per-project data (e.g., project_4.duckdb). PgDataService replaces DuckDBService as the data service backend for written extraction data. Backend currently uses DuckDBService for managing extracted data storage and querying. PgDataService replaces DuckDBService within the Backend as the data storage service. DuckDBService manages Project 14 DuckDB file for extracted data operations. DuckDBService provides database connections and query execution needed by QueryDataSkill. PgDataService is an alternative service managing PostgreSQL connections, complementing DuckDBService for DuckDB database management. QuestionRouter uses the DuckDB Service for executing SQL queries and accessing data. DuckDB Service is defined in backend/app/services/duckdb_service.py. The execute_query method is part of the DuckDB Service. Project Storage is used by the DuckDB Service to store project-specific DuckDB files.

The file prioritizer component is utilized by the batch processor orchestrator to assign tiers and manage processing order. BatchProcessor uses FilePrioritizer to prioritize project files in processing pipeline orchestration. FilePrioritizer uses DiscoveryService outputs to prioritize project files relevant to analytical questions. The File prioritizer is used by the Batch processor orchestrator in the processing pipeline. The Project dashboard uses file prioritization features to show tier badges and organize files. ExtractionCoordinator coordinates extraction processes that are prioritized by FilePrioritizer. StorageService handles file storage and retrieval for FilePrioritizer's prioritization process. File prioritizer uses information in FileUpload columns such as tier and AI summary to assign processing priorities. The File prioritizer capability is validated by the test_file_prioritizer test case.

The Frontend uses FileUpload.svelte UI component for drag-drop file upload.

Logging is needed for findings generation to trace data flow and identify failure points during findings creation. QuestionRouter integration works with FindingsGenerator logic in the agent architecture to process and generate findings. FindingsGenerator logic outputs generated findings via the message streaming format for frontend rendering.

The Frontend Components include the FindingsPanelNew.svelte UI component which serves as a master panel with filtering capabilities for findings. Frontend Integration uses the FindingsPanelNew component to display findings in the agent page. The agentStore.findings data is connected to the FindingsPanelNew component for frontend rendering. The FindingsPanelNew.svelte UI component is part of the Full Findings Visualization Layer serving as a master panel with filtering capabilities. The FindingsPanelNew.svelte UI component is part of the Full Findings Visualization Layer serving as a master panel with filtering capabilities. FindingsPanelNew replaces FindingsBoard in the agent page user interface

The project dashboard contains a folder-grouped file inventory with tier badges and filtering capabilities.

DataLens's frontend, built with SvelteKit, Tailwind, and shadcn-svelte, offers a user interface including login and project pages. It uses a multi-stage Docker build, integrates with backend APIs, supports Danish language, and is deployed containerized alongside PostgreSQL on theo via Coolify. The frontend ensures end-to-end functionality validation before claiming completion. Frontend service is deployed with Docker Compose orchestration.

The Frontend Components include the MetricCard.svelte UI component for KPI display with stats. The Frontend Components include the TrendChart.svelte UI component which renders SVG line charts with grid. The Frontend Components include the OutlierHighlight.svelte UI component for displaying anomaly detection information. The Frontend Components include the FindingsPanelNew.svelte UI component which serves as a master panel with filtering capabilities for findings. The UI Flow is implemented using Frontend components such as DiscoveryFlow, DiscoveryLoading, ConsolidationReview, and ConsolidationCard. The Data Discovery Feature includes Frontend components implementing DiscoveryFlow, DiscoveryLoading, ConsolidationReview, and ConsolidationCard UI components. The Data Discovery Feature includes frontend components consisting of 4 Svelte UI components with beautiful user experience.

The Frontend DiscoveryFlow component is part of the UI Flow for the Data Discovery feature.

The message streaming format is used by the frontend rendering to display agent messages and findings.

The Data Discovery system uses Frontend UI components including DiscoveryFlow.svelte, DiscoveryLoading.svelte, ConsolidationReview.svelte, and ConsolidationCard.svelte for user interaction. The Data Discovery Feature uses Frontend UI components including 4 Svelte components with modern UX. The DiscoveryFlow page uses Frontend UI components as part of the Data Discovery user experience. The Data Discovery System uses Frontend UI components to provide an intuitive user interface with visual join paths and animations. The Frontend catalog dashboard is a planned component that will be built to interact with the DataLens Platform backend. The frontend UI for Data Discovery is validated by the comprehensive E2E test suite.

The frontend/src/lib/components/agent/ChatPane.svelte is a UI component for the IronClaw-powered Agent Mode.

The FindingCard UI component belongs to the IronClaw-powered Agent Mode frontend features.

The FindingsBoard component is part of the frontend UI for IronClaw-powered Agent Mode.

The GDPR warning UI component is integrated into the IronClaw-powered Agent Mode frontend.

MessageBubble component is part of the IronClaw-powered Agent Mode frontend interface.