starry-agent

byBalaji B

the agent has to fill the above details by seeing

Landing
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirement Document
Page 1 of 3

Starry-Agent System Requirements Document

Introduction

This document outlines the system requirements for the "Starry-Agent" project. The purpose of this project is to develop an intelligent agent capable of efficiently transferring and managing data between different interfaces, ensuring accuracy and reliability.

System Overview

The Starry-Agent system is designed to automate the process of data entry by extracting information from a source and populating it into a target form. This system aims to enhance productivity by minimizing manual data entry errors and streamlining workflows.

Functional Requirements

  • As a User, I should be able to upload a text file containing patient data.
  • As a User, I should be able to view the extracted patient data in a read-only format.
  • As a User, I should be able to manually enter or edit patient details in the provided form fields.
  • As a User, I should be able to see the overall progress of the data entry task.

User Personas

  • User: The primary user responsible for uploading files and managing patient data entry.
Page 2 of 3

Visuals Colors and Theme

  • primary: #4A4E69 (Deep Purple)
  • primary_light: #9A8C98 (Lavender)
  • secondary: #F2E9E4 (Soft Beige)
  • accent: #C9ADA7 (Rose)
  • highlight: #F4A261 (Warm Orange)
  • bg: #F7F7FF (Light Gray)
  • surface: rgba(255, 255, 255, 0.9) (White)
  • text: #22223B (Dark Navy)
  • text_muted: #9A8C98 (Muted Lavender)
  • border: rgba(74, 78, 105, 0.2) (Subtle Purple)

Signature Design Concept

The homepage of Starry-Agent will feature an interactive galaxy map where each star represents a different feature or section of the application. Users can click on a star to open a task card, drag to rotate the galaxy, and hover to highlight connections between different features. This concept will be implemented using @react-three/fiber for 3D rendering and gsap for animations, creating an engaging and immersive experience.

Interaction Model & Motion Direction

The landing page will utilize a "parallax" interaction model, providing a layered depth effect as users scroll. Decorative elements will move at different speeds, enhancing the storytelling aspect of the interface. Internal pages will adopt a "static" model to prioritize clarity and ease of use.

Page 3 of 3

Non-Functional Requirements

  • The system should ensure data accuracy during the transfer process.
  • The interface should be responsive and user-friendly.
  • The system should handle large volumes of data efficiently.

Tech Stack

  • Frontend: React for Web
  • Backend: Python, FastAPI
  • Database: MySQL or MariaDB
  • AI Models: GPT 5.4 for user-friendly responses
  • AI Tools: Litellm for LLM Routing
  • Local Orchestration: Docker, docker-compose
  • Server-side Orchestration: Kubernetes

Assumptions and Constraints

  • The system assumes that the input data files are correctly formatted.
  • The system is constrained by the need to integrate with existing healthcare data systems.

Glossary

  • Agent: A software entity that performs tasks on behalf of a user.
  • Parallax: A visual effect where background images move slower than foreground images, creating a sense of depth.
  • 3D Rendering: The process of generating a three-dimensional image from a model.
Landing design preview
Landing: View Galaxy Map
Landing: Explore Features
Upload: Select File
Upload: Submit File
Preview: View Extracted Data
Form: Review Fields
Form: Edit Patient Details
Form: Save Changes
Progress: View Task Status
Progress: Confirm Completion