Handover workspace

ERS, Todo, OfferReview, and Docu in one view

Imported from live server docs, code structure, and deployment notes.

Apr 3, 2026, 12:38 PM

Todo

Product Requirements Document (PRD)

**What I Do Today**

docs/PRD.md

Updated Mar 4, 2026, 3:14 AM

Product Requirements Document (PRD)

Product Name

What I Do Today

Problem Statement

Leaders need clear visibility into where time and energy are spent, where execution drift occurs against plan, and how team focus changes over time.

Target Users

  • Team owners/admins (configure members, schedules, analytics)
  • Team members (log daily work, plan focus, review personal analytics)
  • Language: English
  • Time zone baseline: Asia/Kuala_Lumpur (configurable via env)

Product Goals

  1. Keep daily logging fast on mobile.
  2. Produce reliable personal and team insights.
  3. Detect focus drift (planned vs actual).
  4. Automate recurring reporting.
  5. Maintain baseline security and auditability.

Functional Scope (Implemented)

  1. Authentication + Access Control
  • One-time setup
  • Login/logout
  • Team RBAC roles: OWNER, ADMIN, MEMBER
  1. Daily Execution
  • Activity logs with date/time/category/project/energy/notes
  • Daily dashboard metrics and top focus areas
  • Category/project management
  1. Planning + Drift
  • Planned focus allocation by category/project
  • Alignment score and over/under-focus detection
  1. Analytics
  • Date range analytics
  • Weekly summary page
  • Monthly trend page
  • Energy trend chart
  • Category/project drill-down over time
  1. Team Collaboration
  • Team member create/update-role/remove
  • Team dashboard with member breakdown + audit events
  1. Reporting and Automation
  • CSV/PDF export (personal + team scope, daily/range)
  • Scheduled exports (DAILY, WEEKLY, MONTHLY)
  • Cron/manual execution path
  1. AI Narrative
  • Daily narrative summary generation
  • OpenAI-backed with deterministic fallback
  1. Security and Observability
  • CSRF origin checks for mutating actions
  • In-memory rate limiting
  • Audit log records for critical actions
  1. Quality
  • Automated unit tests for core analytics/time/drift/rate-limit logic

Current Constraints

  • Rate limiting is in-memory (single-node friendly, not distributed)
  • Scheduled exports run through app/cron process (no dedicated queue worker yet)
  • AI narrative quality depends on available logs and optional API key

Next Product Enhancements

  • Invite-based onboarding
  • Distributed rate limiter (Redis)
  • Queue-backed background jobs
  • Email/Slack report delivery