Product Requirements Document

Owner: Product
Reviewers: Engineering, QA, Operations
Status: Active wrapper
Version: 0.1
Last Updated: 2026-09-16
Review Cycle: Per release

The canonical PRD is ../01_PRD — Product Requirements Document.md.

This file exists to place the PRD inside the 10-part documentation structure without duplicating a large source document. When PRD content changes, update the canonical file first, then update derived requirement files in requirements/ if needed.

Current Alignment

The canonical PRD has been reconciled against the current repository state. Implemented, partial and planned items are explicitly labeled there, including:

Auth, RBAC, farm and pond management are present but scope enforcement has known temporary bypasses.
Alerting, water monitoring, farming logs, feeding, reports, IoT ingestion and device command flows are partially implemented.
AI chatbot, AI feeding recommendations, PCR/FCR and scheduled weekly email reports remain planned.
Web and mobile have implemented role-specific shells plus several placeholder or partial feature screens.

Supporting Product Docs

File	Purpose
`SRS.md`	Software requirements entry point and legacy SRS traceability map.
`roadmap.md`	Release and phase roadmap.
`requirements/business-requirements.md`	Business objectives and constraints.
`requirements/functional-requirements.md`	Functional requirement inventory and status.
`requirements/non-functional-requirements.md`	Security, reliability, performance and maintainability requirements.
`requirements/data-requirements.md`	Logical data entities, fields and retention requirements migrated from SRS.
`requirements/business-rules.md`	Product, device, alert, ticket and AI rules migrated from SRS.
`requirements/permission-matrix.md`	Role-by-module permission baseline.
`requirements/acceptance-criteria.md`	SRS acceptance criteria mapped to test ownership.
`requirements/epics-features.md`	Epic and feature grouping.
`requirements/user-stories.md`	User stories by role.