As a Frontend Developer, I want to implement the global theme, color palette, typography, spacing tokens, and component design system aligned with the v2 mock designs so that all pages have a consistent visual identity across the topaz-ai application.
As a Backend Developer, I want to define and run Alembic (or equivalent) database migrations for all MySQL tables — users, research_tasks, task_runs, summaries, and user_preferences — so that the RDBMS layer is fully versioned and all backend APIs have a reliable structured data store. NOTE: frontend pages that depend on this include Dashboard, Settings, Results, and Research.
As a Backend Developer, I want to initialise Weaviate with the required class definitions (KnowledgeNode, Hypothesis, ResearchSummary, etc.) including vectorizer config and cross-references so that the knowledge graph API and autonomous research engine can persist and retrieve semantic data correctly. NOTE: depends on Weaviate service being available; the WeaviateDB knowledge API task (e593e645) depends on this being done first.
As a Frontend Developer, I want to remove the signup and welcome pages from the scaffold so that only pages defined in the user flows remain, keeping the codebase clean and navigation consistent with the intended product experience.
As a user, I want to see a polished Landing page with the Explore Spiral interaction so that I can understand the topaz-ai product and be guided toward signing in, fully aligned with the v2 design mockup.
As a user, I want a fully styled Login page matching the v2 Sign In design so that I can authenticate securely with a visually consistent and intuitive interface aligned with the topaz-ai brand.
As a user, I want a fully implemented Dashboard page matching the v2 design so that I can assign tasks to the AI, view an overview of active research, and navigate to other sections of the topaz-ai application.
As a Backend Developer, I want to implement FastAPI JWT authentication middleware and protected route dependencies so that all API endpoints (task assignment, knowledge graph, query, results, settings) are secured and only accessible to authenticated users. This middleware should validate tokens issued at login and attach the user context to each request.
As a user, I want a fully implemented Research page matching the v2 design so that I can view AI research progress, pause or monitor the AI, and track active research scenarios in real time.
As a user, I want a fully implemented Query page matching the v2 design so that I can ask the AI questions and request insights drawn from the accumulated knowledge graph.
As a user, I want a fully implemented Settings page matching the v2 design so that I can manage and configure AI research summaries, preferences, and system settings from a single interface.
As a Backend Developer, I want to build a FastAPI endpoint for creating and managing AI research task assignments so that the Dashboard can submit new research goals and track their lifecycle in MySQL.
As a Backend Developer, I want to build FastAPI CRUD endpoints for user preferences — including periodic summary toggle, summary interval configuration, and research control flags — so that the Settings page can read and persist user-specific configuration to MySQL. NOTE: the Settings frontend task (d47f239a) depends on this endpoint.
As a Backend Developer, I want to implement a Server-Sent Events (SSE) or WebSocket endpoint that streams live research task progress — including current topic, nodes discovered, hypotheses generated, and status changes — so that the Research page can display real-time AI activity to users without polling. NOTE: the Research frontend task (8b3ddc9c) and Dashboard task (1907a07f) both depend on this for live updates.
As a user, I want a fully implemented Results page matching the v2 design so that I can view AI-generated findings, hypotheses, and intelligence summaries produced from completed research tasks.
As a user, I want a fully implemented Knowledge Graph page matching the v2 design so that I can visually explore nodes, relationships, and concepts stored in WeaviateDB as the AI expands its knowledge.
As an AI Engineer, I want to implement the core autonomous research engine loop so that topaz-ai can independently discover, process, and iterate on research topics without manual intervention, forming the backbone of the subconscious AI system.
As a Backend Developer, I want to build FastAPI endpoints for storing, retrieving, and querying knowledge graph nodes and relationships in WeaviateDB so that all AI research outputs are persisted and explorable on the Knowledge Graph page.
As an AI Engineer, I want to integrate internet search and web scraping tools into the research engine so that topaz-ai can autonomously gather external knowledge from the web and expand its knowledge graph with real-world data.
As an AI Engineer, I want to implement an AI module that generates, scores, and stores hypotheses derived from accumulated research data so that users can view novel insights and inferred conclusions on the Results page.
As a Backend Developer, I want to build a FastAPI endpoint that accepts natural language queries and returns AI-generated insights from WeaviateDB so that the Query page can surface relevant knowledge and analysis to users.
As a Backend Developer, I want to build FastAPI endpoints to retrieve structured research findings, hypotheses, and intelligence summaries so that the Results page can display completed AI research outputs to users.
As a Backend Developer, I want to build FastAPI endpoints to pause, resume, and stop active research tasks so that users can control the AI research loop in real time from the Research page.
As an AI Engineer, I want to configure Langchain and Litellm to intelligently route AI tasks across GPT, Claude, and Gemini models so that the research engine can leverage multiple LLMs with fallback and cost optimization strategies.
As an AI Engineer, I want to implement a periodic summaries feature that automatically generates and stores concise research summaries at configurable intervals so that users can manage and review AI progress from the Settings page.
As a Backend Developer, I want to build a FastAPI endpoint that allows users to selectively re-run or regenerate specific research findings or hypotheses so that stale or low-confidence results can be refreshed without restarting the full research cycle.
No comments yet. Be the first!