Zimo Clan is the participation layer around an agricultural operating layer. HAOS connects operational applications without making unsupported promises about what the Testnet has already proven.
Each layer below has a job. The current Testnet validates selected workflows; it does not claim that every future protocol capability is live.
Participation Layer
Coordinates member participation and community pathways.
Agricultural Operating Layer
Provides the operating context for agricultural applications.
Monitoring Layer
Supports operational reporting, monitoring and agricultural intelligence.
Trust Layer
Holds evidence and verification context for participating farms.
Marketplace Layer
Supports commodity listings, offers and market workflows.
Financial Operations Layer
Represents financial operations and settlement boundaries.
These are architectural requirements and boundaries, not unsupported performance guarantees.
Use clear service boundaries and bounded data flows so new agricultural applications can be added without rewriting the participation layer.
Connect systems through documented interfaces and verified application boundaries.
Expose only the data and operations each application is authorized to use; the website itself has no private API gateway.
Keep ownership, consent, provenance and retention decisions explicit for farm and participant data.
Preserve the source and context of operational and verification records so outcomes can be reviewed.
Keep identity, access control, evidence and financial authorization as separate concerns.
Treat Zimo, HAOS, verification, intelligence and marketplace capabilities as distinct layers.
Make agricultural information usable across supported phones, tablets and desktop browsers.
A participant identity is not the same as a farm verification record or an application permission. Keeping those boundaries separate supports safer data governance and clearer accountability.