<!--
INSTRUCTIONS FOR REQUIREMENTS (FREESTYLE):
- Document user needs and system requirements in any format that works for your project
- Consider using user stories, use cases, or functional specifications
- Make requirements specific and testable
- Number or organize requirements for easy reference
- Focus on what the system should do, not how it should do it
-->

# Requirements Document

## Functional Requirements

<!-- What the system should do -->

### [Requirement Category]

<!-- Group related requirements together -->

## Non-Functional Requirements

<!-- Performance, security, usability, etc. -->

### Performance

<!-- Response times, throughput, scalability requirements -->

### Security

<!-- Authentication, authorization, data protection requirements -->

### Usability

<!-- User experience, accessibility requirements -->

## Business Rules

<!-- Constraints and rules that govern system behavior -->

## Assumptions and Dependencies

<!-- External dependencies and assumptions made -->
