User Tools
architecture:farm_controller:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| architecture:farm_controller:start [2026/01/21 20:31] – [4. Conflict Resolution] bsamuel | architecture:farm_controller:start [2026/01/21 20:32] (current) – [1. Responsibilities] bsamuel | ||
|---|---|---|---|
| Line 13: | Line 13: | ||
| * Aggregate telemetry from Field Controllers: | * Aggregate telemetry from Field Controllers: | ||
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| * Provide a **local operator interface** for monitoring and configuration. | * Provide a **local operator interface** for monitoring and configuration. | ||
| * Validate all operator requests against Field Controller safety rules. | * Validate all operator requests against Field Controller safety rules. | ||
| Line 96: | Line 96: | ||
| ===== 6. Human Interface ===== | ===== 6. Human Interface ===== | ||
| - | * The Farm Controller **must provide a full local UI**: | + | |
| - | - Monitoring dashboards for all irrigation zones | + | - Monitoring dashboards for all irrigation zones |
| - | - Configuration of schedules and thresholds | + | - Configuration of schedules and thresholds |
| - | - Alerts and notifications for operators | + | - Alerts and notifications for operators |
| - | * Operator actions are validated against Field Controller safety rules. | + | * Operator actions are validated against Field Controller safety rules. |
| - | * The interface supports **manual requests**, but these cannot bypass critical safety decisions. | + | * The interface supports **manual requests**, but these cannot bypass critical safety decisions. |
| --- | --- | ||
| Line 107: | Line 107: | ||
| ===== 7. Implementation Notes ===== | ===== 7. Implementation Notes ===== | ||
| - | * Hardware: Industrial-grade single-board computers (e.g., NanoPi, Raspberry Pi). | + | |
| - | * Communication protocols: LAN, WiFi, or cellular for synchronization. | + | * Communication protocols: LAN, WiFi, or cellular for synchronization. |
| - | * Data format: Structured, versioned, and compatible with HQ controller ingestion. | + | * Data format: Structured, versioned, and compatible with HQ controller ingestion. |
| - | * Security: All communications must be encrypted; operator authentication is required. | + | * Security: All communications must be encrypted; operator authentication is required. |
| - | * Scalability: | + | * Scalability: |
| --- | --- | ||
| Line 117: | Line 117: | ||
| ===== 8. Compliance Notes ===== | ===== 8. Compliance Notes ===== | ||
| - | * Any AOFS-compliant Farm Controller **must implement offline operation, federation, logging, and safety validation**. | + | |
| - | * Failure to preserve Field Controller authority or provide audit logs **invalidates compliance**. | + | * Failure to preserve Field Controller authority or provide audit logs **invalidates compliance**. |
| - | * Synchronization conflicts must follow the deterministic resolution rules defined above. | + | * Synchronization conflicts must follow the deterministic resolution rules defined above. |
architecture/farm_controller/start.1769027461.txt.gz · Last modified: by bsamuel
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
