Architecture for community control, legible in the code.
The knowledge belongs to the community. So does the data.
For decades, coastal data has followed an extractive pattern: knowledge flows outward, models are trained elsewhere and results return as products or reports. Benthos is built around a different protocol, where communities govern the data they create.
The people who collect the data decide what leaves the territory. This is a clause in the partnership contract and a constraint in the code, not just an intention. Funders and research partners receive agreed aggregates; raw data stays where it was spoken. Sovereignty lives in the decisions we encode: in how the database is structured, who can access what and how every query is logged. This is where a promise becomes enforceable.
“Sovereignty lives in the schema.
In the structure of the data itself.”
Field organizations lead the relationship with communities. Research institutes shape the methodology. Funders enable the work. Benthos builds the technical layer that carries it. Each role has clear boundaries, ensuring communities retain control while research and funding scale effectively.
Five layers, from field collection to funder reporting. Each one is a place where the line between what stays and what leaves gets drawn.
This is the architecture we are building.
Community chooses what to log, and who logs it. Consent is granular and explicit.
Raw data sits on infrastructure owned and controlled by the community. Data remains strictly within the territory unless explicit consent is granted.
Named keys and a readable audit trail. Access can be revoked in the system itself, instead of relying on informal email requests.
Only agreed indicators cross the territorial boundary into external systems. Aggregates that protect individual identity, using differential privacy where needed.
Reports are agreed exports. Communities see everything that leaves.
Each layer is marked for what it is today, because sovereignty claimed early is sovereignty diluted.
Coastal knowledge moves across four overlapping spheres: universal frameworks like CARE and FAIR, national legislation, territorial context and community-held expertise. Each sphere has its own platforms. The community sphere is where data sovereignty has been least built. That is where Benthos operates: communities at the center, infrastructure orbiting to serve them.
This architecture introduces friction. Onboarding is slower, funders receive aggregates instead of raw data and communities need technical capacity to exercise the rights it preserves. A sovereignty that costs nothing protects nothing.
Sovereignty is an architectural choice about who a system serves, and the discipline to keep that choice legible in the code. That is what Benthos builds.
This thesis builds on the CARE Principles for Indigenous Data Governance (Carroll et al., 2020). We read CARE through an engineering question: where does each commitment land in the code?
It also draws on the literature on data colonialism (Ricaurte, 2019) and on the FAIR Principles (Wilkinson et al., 2016). The differential privacy in layer 04 is Cynthia Dwork's work.
If you see room to refine a layer, or a coastal project
this architecture could serve, reach out directly.