workload-domainlisted

# Workload Domain Skill ## What This Is The workload tracker is a standalone web application for tracking team workload, scoring task complexity, and surfacing overload signals before they become problems. It was built inside `rell-engine` and has since been extracted as its own deployable product. **Locations:** - `rell-eco/rell-engine/engine/workload_engine.py` — Core engine - `rell-eco/rell-workload/` — Standalone deployment --- ## Josefina Context `rell-workload/JOSEFINA_START_HERE.bat` — The workload tracker was deployed for a specific user named Josefina. She is the primary day-to-day operator. The `.bat` file exists to make startup zero-friction for a non-technical operator. When working on workload features, always consider: - Non-technical operator UX (Josefina model: she should click one thing and it works) - The tracker must be honest about overload — no softening the data - Reports should be actionable, not just informational --- ## Scoring System The workload engine scores individual tasks and produces aggregate team load signals. **Config:** `rell-workload/config/scoring.json` **Team Roster:** `rell-workload/config/team-roster.json` Scoring factors include task complexity, priority, time sensitivity, and team member current load. Outputs a normalized score per assignment and a team-level load index. --- ## Stack ``` rell-workload/ ├── run_web.py ← Start the web server ├── engine/ │ ├── workload_engine.py ← Core scoring logic │ └── e