-informational){kind=icon}
Offline-first rural edge computing stack for agritech and environmental monitoring.
castuo-agro-edge is the operational edge layer of the ecosystem. It is designed to run in environments where connectivity is unreliable, sovereignty matters, and telemetry must survive disconnections.
Its scope covers:
- MQTT Telemetry Ingestion: Local sensor data handling.
- Offline Buffering: Data persistence during disconnection periods.
- Hardware Integration: Support for Raspberry Pi gateways and ESP32 nodes.
- Edge Orchestration: Sensor management and local actuation loops.
castuo-agro-edge acts as the EDGE layer, providing field evidence and telemetry to the core platform.
castuo-agro-edge (Edge)
│
├── castuo-evidence (Public Fabric)
│ Evidence verification surface
│
├── CASTÚO-SYSTEM (Private Core)
│ Upstream sync target
│
└── castuo-evolution (experimental)
Governance framework — not the current SSOT
| Layer | Technology |
|---|---|
| Gateway | Python 3.11+, FastAPI |
| Messaging | MQTT (Mosquitto) |
| Buffer | SQLite / TimescaleDB (edge) |
| Hardware | Raspberry Pi, ESP32, LoRaWAN |
| Containers | Docker, Compose |
| AI (optional) | Mistral AI EU |
Following the Evidence-First principle, this repository focuses on providing reproducible field data.
- Implemented: MQTT ingestion, local buffering, and Pi gateway support.
- Planned: Full end-to-end synchronization with GaiaChain/Core.
Maturity is tracked through the G0-G7 Gates defined in the canonical governance of CASTÚO-SYSTEM (Castuo-system/governance/, private). castuo-evolution is an experimental governance and evolution framework; it is not the current source of truth or a deployed control plane.
cp .env.example .env
docker compose up -d
curl http://localhost:8080/health← Profile | → Evidence | → Governance framework (experimental) | → Architecture Docs
- 🌍 Website
- 📡 Edge Stack
Build · Validate · Observe · Document · Evolve
This repository is governed through the CASTÚO-SYSTEM evidence chain. Its current role, visibility boundary, required provenance, security baseline and promotion rules are defined in docs/CASTUO_ARCHITECTURE_GOVERNANCE.md. A repository artifact or green workflow proves only the declared scope; it does not by itself prove certification, production operation, funding, customer contracts or commercial success.
Federation is a TARGET, not a current capability. No second real node, tested exchange or synchronisation evidence has been verified (
FEDERATION_PENDING).
The edge node is an independent trust boundary. Its readiness model is explicit:
| State | Meaning |
|---|---|
LOCAL_OPERATION_IMPLEMENTED |
Local ingestion or buffering exists within the declared repository scope |
PILOT_PREPARED |
A bounded field protocol and evidence package are prepared |
FEDERATION_PENDING |
No second real node, tested exchange or synchronisation evidence has yet been verified |
Target design for offline operation (not a statement of what is implemented; see the evidence links for verified scope): device identity, encrypted local buffering, an idempotent queue, replay protection, revocation and preserved conflicts. Connectivity loss must not turn an unapproved critical action into an approved one. Physical actuation remains blocked without current policy authorisation and, when required, human approval.
This repository is part of the CASTÚO-SYSTEM private-cloud target architecture. Its repository scope does not by itself prove cloud provisioning, DNS, production operation, customer traction, financing, certification or independent validation. The service identity is a governed target boundary until a deployment record, access control, health check, observability, backup, restore, rollback, owner and dated Evidence Center record are published.
The public state model is DOCUMENTED → IMPLEMENTED_LOCAL → TESTED → VALIDATED → OPERATIONAL. OpenClaw and n8n, where referenced, are optional compatibility adapters and not the sovereign governance control plane.\n