WattsWorth Project

Introduction

The WattsWorth project aims to revolutionize the way organizations conduct emergency tabletop drills by leveraging AI to simulate realistic scenarios. This document outlines the system requirements for the WattsWorth project, focusing on scenario templates for fire and IT outages, role clarity through role cards, scoring aligned with HSEEP methodology, compliance documentation in HSEEP format, and constrained generation for risk mitigation.

System Overview

WattsWorth is designed to provide an efficient and cost-effective solution for conducting emergency drills in various facilities such as companies, schools, and hospitals. The system utilizes AI to generate scenarios, inject real-time complications, and simulate external actors, ultimately producing a comprehensive after-action report. The project targets two primary scenarios: fire and IT outages, which represent different ends of the emergency spectrum.

Key Features:

• Scenario generator by facility type
• Live inject engine
• Multi-player web room
• Scored decisions vs. best practice
• Compliance-ready After-Action Report (AAR) export

Functional Requirements as Story Points

• As a User, I should be able to select a scenario template for fire or IT outage to initiate a drill.
• As a User, I should receive role cards with private information and injects to ensure structural role clarity.
• As a User, I should be able to participate in a multi-player web room for collaborative drill execution.
• As a User, I should receive real-time injects during the drill to simulate dynamic scenarios.
• As a User, I should receive a scored evaluation based on HSEEP methodology.
• As a User, I should be able to generate compliance documentation in HSEEP format.
• As a User, I should have access to a corrective-action tracker post-drill.
• As a User, I should be able to view an attendance log and objectives-tested list after the drill.
• As a User, I should be assured that scenario generation is constrained to avoid off-limits categories.

User Personas

• Administrator: Responsible for setting up and managing drills, selecting scenarios, and reviewing reports.
• Participant: Engages in the drill, receives role cards, and interacts with injects.
• Observer: Monitors the drill to provide feedback and ensure compliance with objectives.

Core User Flows

1. Administrator sets up drill:

   • Selects scenario template (fire or IT outage)
   • Configures role cards and injects
   • Initiates the drill

2. Participant engages in drill:

   • Receives role card with private information
   • Interacts with real-time injects
   • Makes decisions based on scenario

3. Post-drill evaluation:

   • System generates scored evaluation based on HSEEP
   • Administrator reviews compliance documentation
   • Corrective-action tracker is updated

Visuals Colors and Theme

• primary: #1E3A8A (Deep Blue)
• primary_light: #3B82F6 (Sky Blue)
• secondary: #F59E0B (Amber)
• accent: #EF4444 (Red)
• highlight: #F97316 (Orange)
• bg: #F3F4F6 (Light Gray)
• surface: rgba(255, 255, 255, 0.8) (White)
• text: #111827 (Dark Gray)
• text_muted: #6B7280 (Muted Gray)
• border: rgba(209, 213, 219, 0.2) (Light Gray)

Signature Design Concept

Interactive Scenario Map

The home page will feature an interactive scenario map where users can visually explore different emergency scenarios. Each scenario (fire, IT outage) will be represented as a distinct interactive icon on the map. Users can click on an icon to open a detailed view of the scenario, including role cards and injects. The map will dynamically update as scenarios are selected, providing a real-time visual representation of the drill's progress.

Landing Hero Motion Brief: The landing page will feature a continuous loop animation showing a facility transitioning from normal operation to an emergency scenario. The animation will depict inputs (e.g., fire alarms, IT alerts) converging on a central control panel, which then transforms to display the drill's outcome. This will be achieved using motion/react for smooth transitions and interactive elements.

Interaction Model & Motion Direction

• Intended Interaction Model: Animated
• The landing page will feature moderate scroll-triggered reveals and hover transitions, enhancing user engagement without overwhelming them with excessive motion.

Non-Functional Requirements

• The system must ensure data privacy and security for all participants.
• The system should be scalable to accommodate multiple simultaneous drills.
• The system should provide high availability and reliability.

Tech Stack

• Frontend: React for Web
• Backend: Python, FastAPI
• Database: MySQL or MariaDB, with alembic for migrations
• AI Models: Claude Sonnet 5 for scenario generation
• AI Tools: Litellm for LLM Routing
• Local Orchestration: Docker, docker-compose
• Server-side Orchestration: Kubernetes

Assumptions and Constraints

• The system assumes that all users have internet access and compatible devices.
• The system is constrained by the need to comply with HSEEP standards for scoring and documentation.
• The system must avoid generating scenarios involving targeted violence or graphic details.

Glossary

• HSEEP: Homeland Security Exercise and Evaluation Program
• AAR: After-Action Report
• IT Outage: A scenario involving the failure of IT systems
• Injects: Real-time complications introduced during a drill to simulate dynamic scenarios

This document provides a comprehensive overview of the WattsWorth project's system requirements, ensuring that all aspects of the project are clearly defined and aligned with the user's needs and expectations.