Governance, Trust, and Decision-Making
By the time a reader arrives here, the paper has established that Prisma organises events that produce real value, and that this value now has a protocol to represent it. What remains is the question underneath both: who decides?
Who decides what system health change — the Aspect — actually means for a given community? Who controls what gets verified on-chain? Who holds the record of what a community has built, the evidence of its own transformation, and on whose terms can that record travel? These are governance questions. In most systems, including many that call themselves decentralised, they are answered by technical architecture rather than by the communities most affected.
This section makes those questions visible and describes how Prisma answers them, not from theory, but from what organising transformation-oriented events across sub-Saharan Africa has actually taught.
The Stack and Where Governance Begins
In Prisma’s nested system, currency at each level is derived from the level below it. Team currency aggregates into hub currency. Hub currency aggregates into network currency. What funders ultimately receive is a fraction of the rate at which that value is growing, not a fixed extraction, but a share proportional to the system’s own regeneration. The whole edifice rests on one thing: whether the Aspect at ground level is honestly defined.
The Aspect is not a technical output. It is the community’s answer to: what are we becoming capable of that we were not before? If that definition is captured or distorted by interests higher up the stack, everything above it is compromised regardless of how sophisticated the contracts are.
The most critical governance act in the protocol is therefore not at the top. It is at the bottom: who participates in defining the Aspect, and how is that definition protected as value moves upward toward funders.
What This Section Covers
Three questions structure the Governance domain:
-
Who controls what gets measured? A community that does not control the definition of its own contribution cannot be said to own it. This section addresses how that right is protected across the full stack. (See: Currency domain, for how this definition is formalised into a verifiable metric.)
-
Who can be trusted with the record? Trust operates at three layers: individual, institutional, and narrative. A system that earns institutional trust while extracting individual data sovereignty has not solved the problem. It has reproduced it in a new form.
-
How are decisions made when the system needs to change? When parameters shift, when hub aggregation changes, when network-level decisions affect ground-level communities, who is in the room, and whose voice carries weight?
What This Section Does Not Cover
Currency design and business model mechanics belong to their respective domains. This section addresses the layer that holds everything together: the conditions of trust that allow any community participating in Prisma’s protocol to do so without surrendering what makes their participation meaningful.
Where the case study evidence that substantiates these claims is still forming, this section says so. That honesty is not a gap in the argument. It is part of what the argument is making. (See: Case Studies.)