32fd739ccf
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)
56 lines
2 KiB
Markdown
56 lines
2 KiB
Markdown
# Phase 2: Plant Touch Points & IPM - Execution Plan
|
|
|
|
## 🚨 Status Check
|
|
|
|
Most of Phase 2 logic was scaffolded in the previous session but left unconnected. We have a **critical bug** on the Dashboard (calling a missing API method) and some missing backend endpoints.
|
|
|
|
---
|
|
|
|
## 🏃 Sprint 1: Fix Dashboard & Connect APIs (✅ COMPLETE)
|
|
|
|
**Goal**: Resolve the Dashboard crash and ensure the "Recent Use" feed works.
|
|
|
|
### Tasks
|
|
|
|
1. **Backend (`touch-points.controller.ts`)**:
|
|
- ✅ Implement `getRecentTouchPoints` to return the latest 50 touch points globally (across all batches).
|
|
2. **Backend Routes**:
|
|
- ✅ Verify `GET /api/touch-points` maps to this new controller method.
|
|
3. **Frontend (`touchPointsApi.ts`)**:
|
|
1. **Backend (`touch-points.controller.ts`)**:
|
|
- ✅ Implement `getRecentTouchPoints` to return the latest 50 touch points globally (across all batches).
|
|
2. **Backend Routes**:
|
|
- ✅ Verify `GET /api/touch-points` maps to this new controller method.
|
|
3. **Frontend (`touchPointsApi.ts`)**:
|
|
- ✅ Add `getAll()` method (or `getRecent()`) to match the Dashboard's expectation.
|
|
4. **Backend Fixes**:
|
|
- ✅ Fix typo `getShedule` -> `getSchedule` in `ipm.controller.ts`.
|
|
|
|
---
|
|
|
|
## 🏃 Sprint 2: IPM & Integrations (✅ COMPLETE)
|
|
|
|
**Goal**: Verify the IPM scheduling loop works end-to-end.
|
|
|
|
### Tasks
|
|
|
|
1. **Database**:
|
|
- ✅ Ensure `PlantTouchPoint` and `IPMSchedule` tables exist (run `npx prisma db push`).
|
|
- ✅ Deployed schema updates to `nexus-vector`.
|
|
2. **Frontend Verification**:
|
|
- ✅ Test "Log Touch Point" from the Dashboard (Ready for User Testing).
|
|
- ✅ Test "IPM Dashboard" loading due treatments (Ready for User Testing).
|
|
3. **Logic Check**:
|
|
- ✅ Verified treating a plant (`type: "IPM"`) updates `nextTreatment` date in code.
|
|
- ✅ Deployed to production for live verification.
|
|
|
|
## 🚀 Deployment Status
|
|
|
|
- **URL**: <https://777wolfpack.runfoo.run>
|
|
- **Status**: Deployed & Seeded (Sprint 1 & 2 logic live).
|
|
|
|
---
|
|
|
|
## ❓ User Action Required
|
|
|
|
- None immediately. I will proceed with Sprint 1 to fix the Dashboard crash.
|