AquaSprint: Mission Control for Subsea Productivity

In a pressurized chamber 30 meters below the surface, every minute of oxygen and electricity matters. AquaSprint is a single-screen dashboard that merges the habitat's environmental telemetry with a curated personal productivity system. It starts each day with a 15-minute "trim" — adjusting task priorities based on remaining supplies, diver availability, and biometric readiness. The crew works in 90-minute sprints, with active noise cancellation from pump hum, followed by 20-minute "drift" periods for maintenance, meals, or comms. The system adapts to decompression schedules and emergency drills without losing progress tracking. It's not just a to-do list; it's a symbiotic copilot for surviving and thriving in an unforgiving environment.

Existing productivity tools assume unlimited internet, constant power, and easy rescheduling. Underwater habitats face latency, power rationing, and psychological stress. Crews report fragmentation: emails pile up when topside link is live, then silence. No tool accounts for the unique constraints of life support (e.g., scrubber maintenance can't be postponed, but creative work can). The itch: a tool that respects the habitat's physical and social boundaries.

• Reduce cognitive overhead of scheduling by auto-adjusting tasks based on life-support urgency.
• Increase deep-work throughput by enforcing 90-minute sprints synchronized across the crew (quiet mode).
• Enable offline-first sync with topside when link is available, with transparent conflict resolution.
• Provide a daily "trim" report that suggests task swaps to match energy levels (using wearables).
• Log all task completions as part of the mission log, automatically.

• Not a general-purpose project manager; no kanban or Gantt charts.
• Not a chat app; comms happen in drift periods, not during sprints.
• Not a medical monitor; it reads but doesn't interpret biometric data.
• Not a replacement for emergency protocols; drills override the scheduler.
• Not designed for use on the surface; it's optimized for low-bandwidth, high-latency.

• Offline-first PWA backbone (React + IndexedDB) syncing via sporadic LoRa/IRIDIUM bursts.
• Custom scheduler engine in Rust (compiled to WASM) for deterministic task prioritization under constraints.
• Wearable API integration (Garmin or custom) to fetch heart rate variability and stress scores.
• Full CI/CD pipeline using offline-ready containers for updates via USB sticks.

• Layered: Core Scheduler (constraint propagation engine) → Task Model (DAG of dependencies with urgency flags) → UI (single-page dashboard with three views: Now, Today, Drift).
• Data flow: Sensors → edge compute → scheduler → priority queue → UI. The scheduler uses a constraint satisfaction algorithm (CSP) with replanning every 15 minutes. Conflicts flagged visually.
• Storage: All data local; topside sync uses CRDTs for seamless merging.

• Crew resistance to rigid sprint timing (mitigation: customizable duration per individual).
• Sensor data noise leading to incorrect energy predictions (mitigation: manual override, average over 3 days).
• Sync failures causing data loss (mitigation: triple redundant local backup, USB export).
• Cognitive load of learning new system during a mission (mitigation: simulation pre-mission, progressive onboarding).

• Should drift periods include mandatory social time? Or keep optional?
• How to handle a crew member who consistently ignores the schedule? (Potential for friction)
• Should the system allow "emergency overrides" that pause all non-critical tasks? (Probably yes)

The concept was developed as part of an NSF proposal that didn't get funded. The team dispersed after the principal investigator took a sabbatical. The codebase remains on a private GitHub repo, about 40% done (core scheduler works, UI is a wireframe). Life moved on, but the problem hasn't gone away.

This would have been ideal for a 2024 NASA analog mission but the budget cycle missed it. Perhaps a student team could pick it up.