Zimo Clan is the participation layer around an agricultural operating layer. HAOS connects operational applications without making unsupported promises about what the platform has already proven.
Each layer below has a job. The platform proves selected workflows; it does not claim that every future protocol capability is live.
Evidence
A coordinator's visit, the record they make, and the photographs behind it.
Monitoring
Daily reports from the farm, batch records, and the reporting a farmer works from.
Production
The husbandry, feeding and cycle management a production run actually consists of.
Movement
Pickup from the farm, routing, and the weights recorded when a harvest is collected.
Sale
Where produce reaches buyers, with orders, dispatch documents and tracking.
Shared assets
Storage, processing and inputs, funded by the member community and used by partner farms.
Money
Wallets, escrow against a named project, and the settlement of a completed cycle.
Accounting
What a cycle produced, what it sold for, and how the outcome was accounted for.
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.