Afritic Open Farming Standard

User Tools

Site Tools

You are here: Afritic Open Water and Farming Standard (AOWFS) » System Architecture Overview
Trace:
architecture:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
architecture:start [2026/01/21 21:04] – [4. Federation / Sync Model] bsamuelarchitecture:start [2026/02/23 01:11] (current) – [8. References] bsamuel
Line 76: Line 76:
 ===== 5. Human Interface Rules ===== ===== 5. Human Interface Rules =====
  
-* All controllers expose interfaces appropriate to their role:   +  * All controllers expose interfaces appropriate to their role:   
-  - Field Controller: embedded status UI, safety alerts, non-critical operator overrides   +    * Field Controller: embedded status UI, safety alerts, non-critical operator overrides   
-  - Farm Controller: full local UI for monitoring, configuration, and federation   +    * Farm Controller: full local UI for monitoring, configuration, and federation   
-  - HQ Controller: multi-farm dashboards, analytics, authorized configuration proposals   +    * HQ Controller: multi-farm dashboards, analytics, authorized configuration proposals   
-* No interface may bypass Field Controller safety rules.  +  * No interface may bypass Field Controller safety rules.  
  
 --- ---
  
-===== 6. Compliance Notes =====+===== 6. Communication Model & Protocol Independence ===== 
 + 
 +  * Controller layers may communicate using one or more standardized protocols (see [[architecture:protocols:start|Communication Protocols & Standards]]) 
 +  * Protocol choice does not define authority 
 +  * Communication transport is strictly separated from control authority 
 + 
 +  * Field Controller authority is defined by architectural rules, not by message origin 
 +  * Remote commands received via MQTT, AMQP, or other protocols must always be validated locally 
 +  * Loss of connectivity must never affect safety-critical irrigation execution 
 +  * Communication failure must default to safe autonomous operation 
 + 
 +  * AOFS architecture is protocol-agnostic 
 +  * Multiple protocols may coexist within a deployment 
 +  * Implementations must ensure auditability of all received and transmitted messages 
 + 
 +--- 
 +===== 7. Compliance Notes =====
  
   * AOFS-compliant deployments **must implement all three layers** as defined.     * AOFS-compliant deployments **must implement all three layers** as defined.  
Line 94: Line 110:
 --- ---
  
-===== 7. References =====+===== 8. References =====
  
   * [[architecture:field_controller:start|Field Controller Layer]]     * [[architecture:field_controller:start|Field Controller Layer]]  
   * [[architecture:farm_controller:start|Farm Controller Layer (Local / Federated)]]     * [[architecture:farm_controller:start|Farm Controller Layer (Local / Federated)]]  
   * [[architecture:hq_controller:start|HQ / Federated Controller Layer]]     * [[architecture:hq_controller:start|HQ / Federated Controller Layer]]  
-  * [[hydraulics|Hydraulic & Water Systems]]  +  * [[hydraulics:start]]  
   * [[electrical|Electrical & Control Interfaces]]     * [[electrical|Electrical & Control Interfaces]]  
   * [[sensors|Measuring, Monitoring & Documentation Systems]]     * [[sensors|Measuring, Monitoring & Documentation Systems]]  
  
architecture/start.1769029472.txt.gz · Last modified: by bsamuel

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki