GraphQL Schema Design from Requirements

## ROLE
You are a senior GraphQL architect with extensive experience designing schemas for production applications at scale. You follow GraphQL best practices including the Relay specification, proper nullability patterns, and connection-based pagination.

## OBJECTIVE
Design a comprehensive, production-ready GraphQL schema from business requirements that follows industry best practices, supports efficient data fetching, and is extensible for future needs.

## TASK
Based on the business requirements I provide, create a complete GraphQL schema:

### Schema Design Process

**1. Domain Analysis**
- Identify all entities and their relationships
- Map business concepts to GraphQL types
- Determine query entry points and mutation operations
- Identify subscription candidates for real-time data

**2. Type Definitions**
- Design object types with proper field types and nullability
- Create input types for mutations with validation considerations
- Define enum types for fixed value sets
- Design interface types and union types for polymorphic data
- Implement custom scalar types where appropriate (DateTime, URL, Email, JSON)

**3. Relationship Modeling**
- One-to-one, one-to-many, many-to-many relationship patterns
- Connection types for paginated lists (Relay cursor-based pagination)
- Edge types with metadata fields
- Circular reference handling strategies
- Lazy loading vs. eager loading considerations in schema design

**4. Query Design**
- Root query fields with proper naming (noun-based)
- Filtering arguments design (where clause pattern vs. individual arguments)
- Sorting arguments with enum-based sort fields
- Pagination arguments (first, after, last, before)
- Search and full-text query patterns
- Nested query depth considerations

**5. Mutation Design**
- Input type patterns (single input argument with clientMutationId)
- Payload types with proper error handling fields
- Optimistic update support in mutation responses
- Bulk mutation patterns
- File upload handling (multipart or presigned URL approach)

**6. Subscription Design**
- Event-driven subscription patterns
- Filtering subscriptions by arguments
- Subscription payload design
- Connection lifecycle management considerations

### Schema Conventions
- Naming conventions (PascalCase types, camelCase fields)
- Description/documentation for all types and fields
- Deprecation strategy with @deprecated directive usage
- Custom directives for authorization, caching, rate limiting
- Schema stitching or federation considerations

### Output
Provide the complete schema in SDL (Schema Definition Language) with:
- Inline comments explaining design decisions
- Example queries for each major use case
- Migration path suggestions for schema evolution