System Requirements Document (SRD)

Project Name: rising-music

1. Introduction

The rising-music project is a comprehensive music distribution platform designed for Lefan Music Recordings. This system aims to empower artists by providing them with tools to distribute their music to major platforms (e.g., Spotify, Apple Music), manage royalties, and analyze audience data. By combining these functionalities, rising-music seeks to streamline the music distribution process while offering valuable insights to artists.

This document outlines the system requirements for rising-music, tailored to meet the needs of artists and administrators. It incorporates features for track uploads, royalty tracking, analytics, and selective re-run capabilities, ensuring a seamless and efficient user experience.

Given the Finnish context of this project, the system will adhere to local regulations and support relevant currencies (e.g., EUR) and time zones (e.g., EET).

2. System Overview

The rising-music platform will serve as a centralized hub for music distribution, royalty management, analytics, and selective re-run capabilities. The system will cater to three primary user personas: Artists, Admins, and General Users.

Key features include:

• Music Distribution: Upload tracks and distribute them to major streaming platforms.
• Royalty Management: Track earnings and manage payouts in EUR.
• Audience Analytics: Provide insights into listener demographics, streaming trends, and platform performance.
• Selective Re-run Capability: Allow users to trigger specific system processes, such as regenerating reports, re-distributing tracks, or regenerating the System Requirements Document (SRD), without affecting unrelated operations.

The platform will be accessible via a web application and a mobile app, ensuring flexibility and convenience for users.

3. Functional Requirements

• As an Artist, I should be able to upload tracks and metadata for distribution.
• As an Artist, I should be able to view my royalty earnings in EUR.
• As an Artist, I should be able to analyze audience data, including demographics and platform-specific performance.
• As an Admin, I should be able to manage artist accounts and approve track uploads.
• As an Admin, I should be able to generate reports on platform-wide performance and earnings.
• As an Admin, I should be able to configure payout schedules and manage royalty disbursements.
• As a User, I should be able to selectively re-run specific processes, such as regenerating reports, re-distributing tracks, or regenerating the System Requirements Document (SRD), without impacting other system operations.
• As a User, I should be able to manually trigger SRD regeneration as part of the selective re-run capability.

4. User Personas

4.1 Artist

• Description: Independent musicians or bands who use the platform to distribute their music and manage their earnings.
• Goals:
  • Distribute music efficiently.
  • Track royalties and earnings.
  • Gain insights into audience behavior.

4.2 Admin

• Description: Platform administrators responsible for managing artist accounts, approving content, and overseeing platform operations.
• Goals:
  • Ensure smooth operation of the platform.
  • Manage artist accounts and content approvals.
  • Generate reports and oversee royalty disbursements.

4.3 General User

• Description: Any user of the platform who may need to trigger specific processes, such as artists or admins.
• Goals:
  • Re-run specific processes without affecting unrelated operations.

5. Visuals Colors and Theme

The rising-music platform will feature a modern, vibrant, and creative design inspired by the dynamic nature of the music industry. The color palette is as follows:

• Background: #1B1F3A (Deep Indigo)
• Surface: #2C2F48 (Charcoal Blue)
• Text: #F5F5F5 (Soft Pearl White)
• Accent: #FF5733 (Fiery Orange)
• Muted: #7A869A (Slate Gray)

This palette creates a sleek and professional look while maintaining a creative and energetic vibe.

6. Signature Design Concept

The rising-music homepage will feature an interactive soundwave visualization that reacts dynamically to user interactions.

Key Features:

1. Dynamic Soundwave Animation:

   • A large, colorful soundwave spans the homepage, pulsating gently in sync with ambient background music.
   • As users hover over different sections of the soundwave, it morphs into interactive hotspots, revealing key features of the platform (e.g., "Distribute Your Music," "Track Your Royalties," "Analyze Your Audience").

2. Track Upload Simulation:

   • A prominent "Upload Your Track" button triggers a playful animation where a vinyl record spins, symbolizing the upload process.

3. Micro-Interactions:

   • Buttons and icons respond with subtle animations, such as glowing edges or smooth transitions, to enhance the user experience.

4. Color Shifts:

   • The background subtly transitions between shades of Deep Indigo and Charcoal Blue, creating a calming yet dynamic visual effect.

This design concept ensures that the homepage is not only visually stunning but also highly engaging, leaving a lasting impression on users.

7. Non-Functional Requirements

• Performance: The platform must handle up to 10,000 concurrent users without performance degradation.
• Scalability: The system should be scalable to accommodate future growth in user base and data volume.
• Localization: Support for Finnish language and EUR currency.
• Security: Implement robust security measures, including data encryption and secure authentication protocols.
• Availability: Ensure 99.9% uptime for both web and mobile applications.
• Selective Re-run Capability: Ensure that user-triggered re-runs, including SRD regeneration, are isolated and do not impact unrelated system processes.

8. Tech Stack

Frontend

• Web: React
• Mobile App: React Native

Backend

• Language: Python
• Framework: FastAPI

Database

• RDBMS: MySQL (with Alembic for migrations)

AI Models

• GPT 5.4: For user-friendly responses.
• Claude 4.6 Opas: For analytics and coding-related tasks.

AI Tools

• Litellm: For LLM routing.
• Langchain: For advanced AI workflows.

Orchestration

• Local: Docker, docker-compose
• Server-Side: Kubernetes

9. Assumptions and Constraints

• The platform will initially target Finnish users but may expand globally in the future.
• Royalty payments will be processed in EUR only.
• The system will comply with GDPR regulations for data privacy.
• Artists will be responsible for ensuring their uploaded content adheres to copyright laws.
• Selective re-run processes, including SRD regeneration, will be limited to specific operations, such as report regeneration or track re-distribution.

10. Glossary

• Artist: A user who uploads and distributes music via the platform.
• Admin: A user responsible for managing the platform and overseeing operations.
• Royalty: Earnings generated from music streams or sales.
• Metadata: Information about a track, such as title, artist name, and genre.
• GDPR: General Data Protection Regulation, a European Union law on data privacy.
• Selective Re-run Capability: A feature allowing users to re-trigger specific processes, such as SRD regeneration, without affecting unrelated operations.