malty/ca-grow-ops-manager
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ca-grow-ops-manager/docs/PHASE-4-PLAN.md
fullsizemalt 32fd739ccf
Some checks failed
Deploy to Production / deploy (push) Failing after 0s
Details
Test / backend-test (push) Failing after 0s
Details
Test / frontend-test (push) Failing after 0s
Details
feat: Complete Phases 8-13 implementation 
Phase 8: Visitor Management
- Visitor/VisitorLog/AccessZone models
- Check-in/out with badge generation
- Zone occupancy tracking
- Kiosk and management pages

Phase 9: Messaging & Communication
- Announcements with priority levels
- Acknowledgement tracking
- Shift notes for team handoffs
- AnnouncementBanner component

Phase 10: Compliance & Audit Trail
- Immutable AuditLog model
- Document versioning and approval workflow
- Acknowledgement tracking for SOPs
- CSV export for audit logs

Phase 11: Accessibility & i18n
- WCAG 2.1 AA compliance utilities
- react-i18next with EN/ES translations
- User preferences context (theme, font size, etc)
- High contrast and reduced motion support

Phase 12: Hardware Integration
- QR code generation for batches/plants/visitors
- Printable label system
- Visitor badge printing

Phase 13: Advanced Features
- Environmental monitoring (sensors, readings, alerts)
- Financial tracking (transactions, P&L reports)
- AI/ML insights (yield predictions, anomaly detection)
2025-12-11 00:26:25 -08:00

1.5 KiB
Raw Blame History

Phase 4: Tasks & Scheduling - Implementation Plan

Goal

Implement the operational nervous system of the facility: Task Templates (SOPs), Scheduling (Recurring & One-off), and Execution (Staff Workflow), as defined in specs/tasks-and-scheduling.md.

🏃 Sprint 1: Task Templates (Standard Operating Procedures)

Objective: Allow Head Grower to define how work should be done.

  • Backend:
    • TaskTemplatesController: CRUD for templates.
    • Support "Room Type" association (e.g. "Veg" templates only show for Veg rooms).
  • Frontend:
    • SOP Manager: Library view of all task templates.
    • Template Creator: Form to define title, instructions, materials, and recurrence defaults.

🏃 Sprint 2: Scheduling & Assignment

Objective: Assign work to Rooms and Batches.

  • Backend:
    • TasksController: Create tasks from templates.
    • Logic to inherit properties (Batch ID, Room ID) when a task is created in context.
  • Frontend:
    • Quick Task: "Add Task" button on Batches and Rooms.
    • Task Calendar: View upcoming work.

🏃 Sprint 3: Staff Execution ("My Tasks")

Objective: The daily workflow for growers.

  • Frontend:
    • Today's Tasks UI: High-visibility list of work due today.
    • Task Filter: "My Tasks" vs "All Tasks".
    • Completion Flow: Mark complete, add notes, upload photo.

Technical Dependencies

  • Existing Task and TaskTemplate Prisma models are ready.
  • Need to ensure batchId and roomId are correctly propagated.