Main Page: Difference between revisions
No edit summary |
No edit summary |
||
| Line 36: | Line 36: | ||
</div> | </div> | ||
<div class="hbox-row"> | |||
{{Header box | {{Header box | ||
| Line 56: | Line 58: | ||
* Transparent and auditable | * Transparent and auditable | ||
}} | }} | ||
{{Header box | |||
| title = Start Here | |||
| color = yellow | |||
| body = | |||
If you are new to AOWIS, begin with: | |||
* [[Concepts:Design_Philosophy|Design Philosophy]] | |||
* [[Standard:Definitions|Definitions]] | |||
* [[Standard:Normative_Requirements|Normative Requirements]] | |||
* [[Modules:Module_Template|Module Template]] | |||
* [[AOWIS:Contributor_Guide|Contributor Guide]] | |||
* [[AOWIS:Writing_Style_Guide|Writing Style Guide]] | |||
These pages explain how to read, use, and contribute to the standard. | |||
}} | |||
</dìv> | |||
{{Header box | {{Header box | ||
| Line 80: | Line 100: | ||
}} | }} | ||
== Governance & Legitimacy == | == Governance & Legitimacy == | ||
Revision as of 06:07, 18 March 2026
AOWIS provides a unified framework...
- power is unreliable
- connectivity is intermittent
- equipment is diverse or aging
- trained staff may be limited
- safety and autonomy are essential
AOWIS enables systems that continue working safely — even when everything else fails.
Many communities rely on infrastructure that is fragile, manually operated, or dependent on unstable networks. AOWIS addresses this by defining:
- offline‑first operation
- human‑in‑the‑loop control
- safe fallback behavior
- modular, extensible logic
- shared infrastructure models
- transparent governance
The goal is to make essential systems **robust, maintainable, and locally operable**.
AOWIS is built around a three‑layer control model:
- Field Controller – Local, autonomous, safety‑critical
- Farm Controller – Coordination, scheduling, logic
- HQ Controller – Oversight, reporting, governance
Core principles include:
- Offline‑first
- Measurement‑driven
- Fail‑safe by design
- Human‑operable at all times
- Modular and extensible
- Transparent and auditable
If you are new to AOWIS, begin with:
- Design Philosophy
- Definitions
- Normative Requirements
- Module Template
- Contributor Guide
- Writing Style Guide
These pages explain how to read, use, and contribute to the standard.
</dìv>
The AOWIS standard is organized into dedicated namespaces. These sections form the technical backbone of the project.
- [[Standard:|Standard]] – Normative requirements and definitions
- [[Concepts:|Concepts]] – Philosophy, rationale, and real‑world context
- [[Architecture:|Architecture]] – System structure and controller design
- [[Infrastructure:|Infrastructure]] – Physical systems and components
- [[Measurement:|Measurement]] – Sensors, manual readings, derived values
- [[Data:|Data]] – Data models, logs, sync formats
- [[Operations:|Operations]] – Runtime logic and decision hierarchy
- [[Modules:|Modules]] – Domain‑specific extensions
- [[Databases:|Databases]] – Federated knowledge bases
- [[Governance:|Governance]] – Certification, compliance, licensing
- [[Training:|Training]] – Human capacity building
- [[Reference:|Reference]] – Examples, glossary, FAQ
For a full overview, see the Table of Contents.
Governance & Legitimacy
AOWIS includes a transparent governance model to ensure:
- open participation
- clear certification processes
- stable versioning
- long‑term protection of the standard
See: [[Governance:|Governance]].
Real‑World Impact
AOWIS is designed for practical use in:
- rural water systems
- smallholder agriculture
- community irrigation
- livestock and poultry systems
- greenhouses and controlled environments
Case studies and implementation examples can be found in the [[Reference:|Reference]] namespace.
Navigation
AOWIS is an open, evolving standard. Contributions are welcome.
