Update HA_Architect.md with SCADA-specific guidance
This commit is contained in:
@@ -1,4 +1,4 @@
|
|||||||
# HA_Architect — Role Instructions
|
# HA_Architect – Role Instructions
|
||||||
|
|
||||||
## Primary Responsibilities
|
## Primary Responsibilities
|
||||||
|
|
||||||
@@ -19,6 +19,11 @@
|
|||||||
- Work closely with `HA_Planner` on technical planning
|
- Work closely with `HA_Planner` on technical planning
|
||||||
- Guide `HA_Coder` and `HA_Reviewer` on architectural concerns
|
- Guide `HA_Coder` and `HA_Reviewer` on architectural concerns
|
||||||
|
|
||||||
## Project-Specific Notes
|
## Project-Specific Notes (SCADA for Small Water Systems)
|
||||||
|
|
||||||
[Add any project-specific architectural principles or constraints here]
|
- Prioritize low-egress data design (heavy local summarization on Raspberry Pi edge devices).
|
||||||
|
- Architecture must support hybrid AI: small on-device models + larger cloud models for complex reasoning.
|
||||||
|
- Strong emphasis on Monitored Objects as a first-class concept.
|
||||||
|
- Multi-tenancy support for both individual system owners and professional operators.
|
||||||
|
- Hardware constraints (Raspberry Pi 5 + cellular HAT) are first-class architectural concerns.
|
||||||
|
- Telemetry strategy (immutable core signals vs optional signals) must be reflected in the data and alert architecture.
|
||||||
Reference in New Issue
Block a user