System Requirements Document

1. Introduction

This document outlines the system requirements for the "Pray Across America" web application. The application is designed to facilitate a structured prayer assignment system where users are assigned a church each week to pray for, ensuring that every church in America is regularly prayed for by believers across the country.

2. System Overview

The "Pray Across America" platform is a full-stack web application that assigns users one church per week across the United States to pray for. The assignment is based on a rotating weekly state schedule. The application is not a social network, leaderboard system, or gamified app; it is a structured prayer assignment system.

3. Functional Requirements

User Stories

• As a user, I want to sign up with my email and password to access the platform.
• As a user, I want to log in to the platform using my credentials.
• As a user, I want to see the current week and the current U.S. state for prayer assignments.
• As a user, I want to click "Get My Church" to receive a church assignment in the current state.
• As a user, I want to view the church page with details such as name, address, state, website, and social links.
• As a user, I want to click "Pray Now" to start my prayer session.
• As a user, I want to complete my prayer and click "I Prayed" to log it in the system.
• As a user, I want to optionally share my prayer activity on social media.
• As a user, I want to receive a new church assignment each week based on the rotating state schedule.
• As a user, I want to ensure that I do not receive the same church assignment repeatedly until necessary (Anti-Repetition Rule).
• As a user, I want the system to prioritize churches that have been prayed for less frequently (Church Assignment Philosophy).
• As a user, I want the system to behave consistently given the same user, week, and state unless randomness is explicitly applied (Determinism Rule).
• As a user, I want the system to prioritize prayer over analytics, churches over users, encouragement over metrics, and unity over competition (Mission Safeguard).
• As a user, I want the system to avoid any form of gamification, such as leaderboards or scoring systems (STRICT ANTI-GAMIFICATION RULES).
• As a user, I want to see a simple prayer prompt for the pastor, congregation, and community when I click "Pray Now".

• As a user, I want to generate a shareable message after completing my prayer.
• As a user, I want to have access to a landing page with a headline, subtext, and call-to-action to start praying.

4. User Personas

• Believer: An individual who wants to participate in the prayer assignment system by praying for different churches across America each week.

5. Core User Flows

Sign-Up Flow

1. User navigates to the sign-up page.
2. User enters email and password.
3. User submits the form to create an account.

Login Flow

1. User navigates to the login page.
2. User enters email and password.
3. User submits the form to access their account.

Weekly Church Assignment Flow

1. User logs in and views the dashboard.
2. User sees the current week and state.
3. User clicks "Get My Church" to receive an assignment.
4. System assigns a church based on the current state and fairness logic.
5. User views the church page with details.

Prayer Flow

1. User clicks "Pray Now" on the church page.
2. User sees prayer prompts for the pastor, congregation, and community.
3. User completes the prayer and clicks "I Prayed".
4. System logs the prayer activity.

Share Flow

1. After logging a prayer, user sees a shareable message.
2. User can copy the message or share it on social media.

6. Visuals Colors and Theme

• Professional and calming colors such as blues and greens to reflect the spiritual and peaceful nature of the application.

7. Signature Design Concept

• Clean and minimalistic design focusing on ease of use and clarity of information.

8. Interaction Model & Motion Direction

• Simple and intuitive interactions with smooth transitions between pages and actions.

9. Non-Functional Requirements

• The system must be reliable and handle multiple users simultaneously.
• The application should be compatible with Replit for deployment.
• The system must ensure data integrity and security, especially for user credentials.

10. Tech Stack

• Frontend: React + Vite
• Backend: Node.js + Express
• Database: PostgreSQL
• ORM: Prisma (or SQL if simpler)
• Auth: Simple email/password system (or Clerk if easier)
• Deployment: Replit compatible

11. Assumptions and Constraints

• The system assumes users will self-report their prayer activities.
• The application must not include any gamification elements.
• The system must function with partial data for churches.

12. Glossary

• MVP: Minimum Viable Product
• ORM: Object-Relational Mapping
• UUID: Universally Unique Identifier

This document serves as the comprehensive guide for developing the "Pray Across America" application, ensuring all specified requirements are met.