Business Rules
Owner: Product
Reviewers: Domain, Engineering, QA
Status: Draft — migrated from legacy SRS
Version: 0.1
Last Updated: 2026-09-16
Review Cycle: Per product rules change
Access And Data Scope
| Code |
Rule |
Current Status |
| BR-01 |
Each user has one primary role in the current scope; overlapping roles are not supported unless explicitly redesigned. |
PARTIAL |
| BR-02 |
Every data query must be filtered by role and assigned farm/pond/ticket scope. |
PARTIAL |
| BR-03 |
Users must not view, export, receive notifications for or ask chatbot questions about data outside their allowed scope. |
PARTIAL |
| BR-04 |
Disabled accounts cannot log in, but historical data and audit logs must remain available. |
PARTIAL |
Water Threshold Defaults
These defaults are legacy SRS/domain inputs and require production confirmation before being treated as final.
| Metric |
Default Reference Threshold |
Suggested Action |
Current Status |
| pH |
7.5-8.5 |
Low: lime/algae support. High: water exchange/reduce algae. |
TBD |
| DO |
Greater than 4 mg/L |
Low: start aeration/oxygen and reduce feeding. |
TBD |
| Salinity |
5-30 ppt and daily change no more than 5 ppt |
Adjust water if outside range or changing quickly. |
TBD |
| Algae/ORP |
90-300 mV |
Low: probiotics/aeration. High: reduce algae. |
TBD |
| Alkalinity |
80-180 mg/L |
Low: mineral support. High: water exchange. |
TBD |
| Temperature |
23-32 C |
Low: cover/heat. High: fan/aeration/water exchange. |
TBD |
Device Control
| Code |
Rule |
Current Status |
| BR-05 |
Every device command must log requester, time, command, execution status and response. |
PARTIAL |
| BR-06 |
If a device does not respond within configured X seconds, the system must create a device error alert. |
PARTIAL |
| BR-07 |
Auto mode must not override a manual command for configured Y minutes after user action. |
PLANNED / PARTIAL |
| BR-08 |
Device control permission must consider role, farm/pond scope and system configuration. |
PARTIAL |
Ticket And Escalation
| Code |
Rule |
Current Status |
| BR-09 |
Ticket states are New, Accepted, In Progress and Closed. |
PARTIAL |
| BR-10 |
Creating a technical ticket must notify configured technical recipients and supervisors. |
PARTIAL |
| BR-11 |
Tickets past SLA must escalate to Admin and configured technical supervisors. |
PARTIAL |
| BR-12 |
Environmental alerts past T1 and device alerts past T2 must escalate according to configuration. |
PARTIAL |
AI And Chatbot
| Code |
Rule |
Current Status |
| BR-13 |
Chatbot may use only approved handbook content and farm/pond data the user can access. |
PLANNED |
| BR-14 |
Image analysis is preliminary; chatbot must not give definitive disease diagnosis without technician confirmation. |
PLANNED |
| BR-15 |
Chatbot answers must show source references and/or confidence when possible. |
PLANNED |
| BR-16 |
AI feeding suggestion is a recommendation; users may override it. |
PLANNED |
| BR-17 |
If confidence is low or the issue is serious, chatbot must suggest KTV contact or ticket creation. |
PLANNED |