System Requirements Document for adams-plan

1. Introduction

The "Aura iOS" is an intelligent, native iOS daily planner assistant designed to operate using Apple Design Guidelines and native iOS scheduling logic. It aims to take raw, unstructured inputs from users, automatically categorize them into distinct iOS-tailored operational buckets, output time-blocked schedules with exact local push notification triggers, provide grounded daily motivation, and curate global recommendations for theater, drama, and literature.

2. System Overview

Aura iOS is a native iOS application that functions as a daily planner and cultural companion. It processes user inputs such as tasks, voice memos, or ideas, categorizing them into four operational categories: Deep Work, Admin & Logistics, Health & Wellbeing, and Cultural & Leisure. The app generates time-blocked schedules with notifications and provides cultural recommendations. The system is designed to follow Apple's Human Interface Guidelines and utilizes native iOS features like UNUserNotificationCenter and Live Activities.

2a. Product Interpretation and Delivery Boundary

Aura iOS is delivered as a native iOS application with a focus on intelligent scheduling and cultural recommendations. It requires user authentication for accessing personalized features and supports self-service enrollment. The app operates within the constraints of Apple's design and scheduling guidelines, ensuring a seamless user experience. The application does not support external or provider-owned interactions, maintaining all functionalities within the app's ecosystem.

2b. Source Content Inventory

Not applicable as no explicit content source directive is provided.

2c. Page Content and Component Coverage

Landing

• Purpose: Introduce Aura iOS, its daily-planning purpose, and cultural companion capabilities.
• Components:
  • Overview of features
  • Introduction to the app's capabilities

Login

• Purpose: Allow returning users to verify their identity and resume their saved plans and preferences.
• Components:
  • Username and password fields
  • "Forgot Password" option

Sign Up

• Purpose: Enable new users to enroll and start using the planner.
• Components:
  • Registration form
  • Terms and conditions acceptance

Dashboard

• Purpose: Serve as the daily hub summarizing the current plan and routing to other functionalities.
• Components:
  • Summary of the day's schedule
  • Quick links to Planner, Schedule, Reflections, Notifications, and Culture pages

Planner

• Purpose: Workspace for entering raw tasks, voice memos, and ideas.
• Components:
  • Input fields for tasks and memos
  • "Plan My Day" button to invoke automatic categorization

Schedule

• Purpose: Display the revisitable daily schedule.
• Components:
  • Time ranges, durations, category emojis, and Focus Modes
  • Grouping rules for tasks

Notifications

• Purpose: Manage notifications and actions.
• Components:
  • List of notifications with exact local triggers
  • Actions to mark tasks done or snooze

Reflections

• Purpose: Provide morning and evening reflections.
• Components:
  • Display of dynamic micro-reflections
  • Input for user reflections

Culture

• Purpose: Browse global literature, theater, drama, and cultural-event recommendations.
• Components:
  • List of recommendations with explanations
  • Visit & Experience Tags for each recommendation

3. Functional Requirements

1. As a Daily Planner User, I should be able to enter raw daily tasks, voice memos, or ideas as planning input.

   • Provenance: Explicit
   • Lifecycle: Initiate input, receive categorized output
   • Observable Result: Tasks categorized into operational buckets

2. As a Daily Planner User, I should see my inputs automatically segregated into four operational categories: Deep Work, Admin & Logistics, Health & Wellbeing, and Cultural & Leisure.

   • Provenance: Explicit
   • Lifecycle: Input processing, category assignment
   • Observable Result: Categorized task list

3. As a Daily Planner User, I should receive a time-blocked daily schedule with time range, category emoji, task name, estimated duration, and target Focus Mode.

   • Provenance: Explicit
   • Lifecycle: Schedule generation, notification setup
   • Observable Result: Display of daily schedule

4. As a Daily Planner User, I should receive high-priority notifications for Deep Work tasks, batched into single deep blocks.

   • Provenance: Explicit
   • Lifecycle: Notification setup, task execution
   • Observable Result: High-priority notifications

5. As a Daily Planner User, I should see Admin & Logistics tasks grouped into rapid-fire 15–30 minute execution windows.

   • Provenance: Explicit
   • Lifecycle: Task grouping, execution
   • Observable Result: Grouped task list

6. As a Daily Planner User, I should receive notifications with exact local triggers, concise titles, actionable bodies, and motivational micro-cues.

   • Provenance: Explicit
   • Lifecycle: Notification setup, task execution
   • Observable Result: Actionable notifications

7. As a Daily Planner User, I should be able to mark notifications as done or snooze them by 15 minutes.

   • Provenance: Explicit
   • Lifecycle: Notification interaction
   • Observable Result: Updated notification status

8. As a Daily Planner User, I should receive grounded morning and evening micro-reflections.

   • Provenance: Explicit
   • Lifecycle: Reflection generation
   • Observable Result: Display of reflections

9. As a Daily Planner User, I should receive global literature and book recommendations with explanations matching my evening energy.

   • Provenance: Explicit
   • Lifecycle: Recommendation generation
   • Observable Result: Display of recommendations

10. As a Daily Planner User, I should receive global theater and stage-drama recommendations with Visit & Experience Tags.

    • Provenance: Explicit
    • Lifecycle: Recommendation generation
    • Observable Result: Display of recommendations with tags

11. As a Daily Planner User, I should be able to use the command "Plan My Day" to initiate the planning process.

    • Provenance: Explicit
    • Lifecycle: Command execution
    • Observable Result: Initiated planning process

12. As a Daily Planner User, I should be able to enroll and verify my identity to access personalized features.

    • Provenance: Required Inference
    • Lifecycle: Enrollment and verification
    • Observable Result: Access to personalized features

4. User Personas

Daily Planner User

• Product Context: Uses Aura iOS to organize daily tasks, receive notifications, and explore cultural recommendations.
• Primary Goal: Efficiently manage daily tasks and explore cultural activities.
• Distinct Responsibilities:
  • Enter raw tasks and ideas
  • Review categorized and time-blocked schedules
  • Act on scheduled prompts
  • Engage with morning and evening reflections
  • Explore global cultural recommendations
• Interactions:
  • Inputs tasks and ideas
  • Receives and acts on notifications
  • Engages with cultural content
• Observable Success: Completion of daily tasks and engagement with cultural activities

5. Core User Flows

5.1 Entering Tasks and Ideas

1. Start: User opens the Planner page.
2. Action: User enters tasks, voice memos, or ideas.
3. Result: Tasks are automatically categorized.
4. Next Step: User reviews categorized tasks on the Dashboard.

5.2 Reviewing Daily Schedule

1. Start: User accesses the Schedule page.
2. Action: User reviews the time-blocked schedule.
3. Result: User sees tasks with time ranges and Focus Modes.
4. Next Step: User acts on scheduled tasks.

5.3 Receiving and Acting on Notifications

1. Start: User receives a notification.
2. Action: User marks the task as done or snoozes it.
3. Result: Notification status is updated.
4. Next Step: User continues with the next task.

5.4 Engaging with Reflections

1. Start: User opens the Reflections page.
2. Action: User reads morning or evening reflections.
3. Result: User gains insights or motivation.
4. Next Step: User applies reflections to daily routine.

5.5 Exploring Cultural Recommendations

1. Start: User navigates to the Culture page.
2. Action: User browses literature and theater recommendations.
3. Result: User selects a recommendation with a Visit & Experience Tag.
4. Next Step: User engages with the selected cultural activity.

6. Visuals Colors and Theme

• Muse: Jony Ive
• Palette (light mode):
  • Background: #F5F5F7
  • Surface: #FFFFFF
  • Text: #1C1C1E
  • Primary: #D1D1D6
  • Accent: #FF3B30
  • Muted: #8E8E93
• Typography:
  • Headings: Inter Tight — Light weights
  • Body: SF Pro Text
  • Scale: 1.414 modular
• Shape Language: Soft continuous-curve radii, wide margins
• Layout: Single-column focus with generous whitespace
• Imagery: Studio-lit renders and macro details on plain grounds

7. Signature Design Concept

The public entry page will feature a single product-focused hero with oversized type or a perfectly lit object on a soft neutral background. The design will use generous whitespace and a single focal point to guide user attention, with hairline dividers to separate content.

8. Interaction Model & Motion Direction

• Interaction Model: Static
• Motion Tempo: Restrained
• Hero Dimensionality: Layered_2d
• Landing Hero Motion Brief: A single product-focused hero with oversized type, using slow, physical easing and reveal-on-scroll of one subject.

9. Non-Functional Requirements

• Native iOS Experience: The app must adhere to Apple Design Guidelines and native iOS scheduling logic.
• Performance: The app should efficiently process inputs and generate schedules without noticeable delay.
• Security: User data must be securely stored and accessed only by authenticated users.

10. Tech Stack

• Frontend: Swift (iOS)
• Backend: Python/FastAPI
• Storage: SQLite or Core Data for local storage
• Deployment: Docker/docker-compose

11. Assumptions and Constraints

• Assumption: Users have an iOS device with notification permissions enabled.
• Constraint: The app must function offline with limited features, syncing data when online.

12. Glossary

• Deep Work: High-impact, high-focus tasks requiring concentration.
• Admin & Logistics: Routine tasks such as calls and emails.
• Health & Wellbeing: Activities promoting physical and mental health.
• Cultural & Leisure: Activities related to arts and culture.
• Visit & Experience Tag: A label indicating how a cultural recommendation can be experienced (Live Visit, Read Script, Digital Stage).