UX Work Coordination
UX Work Coordination
Sprint 21 makes the internal operating system easier to read and rehearse. The app now has a consistent status language, human-readable summaries, raw developer details behind disc
Use this when you need a quick orientation to UX Work Coordination.
Sprint 21 makes the internal operating system easier to read and rehearse. The app now has a consistent status language, human-readable summaries, raw developer details behind disclosure panels, and first-class routes for tasks, approvals, notifications, comments, settings, and manager rehearsal.
Active Surfaces
/dashboard/tasksfor internal work coordination./dashboard/approvalsfor human approval requests./dashboard/notificationsfor internal OS notifications./settingsfor personal settings and system administration./dashboard/rehearsalfor manager rehearsal readiness.sprint-21b-remediation.mddocuments the corrective pass for summaries, high-priority task visibility, approval bridge queues, notification bell, comments, and Settings gates.sprint-21c-remediation.mddocuments CRM detail comments, Developer details consistency, and mobile notification bell smoke coverage.- Logistics/fleet readiness is visible through placeholders in Tasks, Approvals, Notifications, Settings, Command Center, and Manager Rehearsal.
Safety Boundaries
- Task completion records work status only.
- Approval decisions record a human decision only.
- Notifications and comments are internal only.
- Settings changes are permissioned and activity logged.
- Manager rehearsal feedback creates System QA issues.
- No external integrations, external messages, production deployment, production secrets, autonomous AI, or destructive approval automation were added.
- No live GPS tracking, driver app, map API, automated delivery messages, customer delivery tracking, or full Logistics/Fleet module was added.
Visual Language
Status chips summarize state, priority, risk, source, manual action, AI/draft status, and disabled-placeholder features. Pages should prefer plain-language summaries for staff and keep raw JSON or developer metadata inside Developer details.
Developer Details
- Source
- apps/docs/content/ux-work-coordination/README.md
- Owner
- Module Owner
- Status
- Current
- Module
- UX Work Coordination
- Related route
- /dashboard/tasks