HYPHA
Designing modular governance as a fractal system: each space carries its own agreements, members, and treasury — and the same pattern can repeat at every scale.
Decentralization creates a design problem: where does governance live?
Traditional organizations concentrate many governance functions in managers, departments, policies, and central administration. When those structures are removed or distributed, the work does not disappear.
Groups still need to know who belongs, what has been agreed, how resources are held, how decisions are made, and how participation can end.
The product challenge was to make those functions explicit without recreating a single central authority — and without forcing every group to invent governance from scratch.
A space is the basic governance cell.
Instead of treating governance as one organization-wide layer, I modeled it as a repeatable unit. Every space contains the same three core primitives: agreements, members, and treasury.
Agreements
What is this space for? What rules, commitments, and boundaries define participation?
Members
Who belongs here? What roles, rights, responsibilities, and permissions do they carry?
Treasury
What resources does this space steward, and under what authority can they move?
SPACE
A bounded governance context with its own agreements, membership, resources, and decision process. A space can also contain other spaces.
The same governance pattern can exist at every scale.
A project team, working circle, local chapter, or whole organization can each be represented as a space. The structure does not change when the scale changes; only the context does.
members
treasury
Govern close to the work
Each space can define its own operating context rather than inheriting every decision from a central layer.
Repeat the structure, not the rules
Spaces share a common product model while their agreements and participation conditions can differ.
Spaces can contain spaces
Governance becomes modular: smaller units can be nested inside larger contexts without losing their own identity.
Every space needs a clear way to enter, decide, and exit.
The next step was to model participation as three reusable modules. These modules give each space a complete lifecycle rather than treating membership as a static permission.
Enter
Make the boundary of the space explicit: what someone needs to understand, accept, or receive before becoming a member.
Decide
Give members a legible path for turning an issue into a recorded decision without hiding who has authority.
Exit
Treat leaving as a designed transition: clarify obligations, permissions, resources, and what remains in the shared record.
A decision is a stateful object, not just a vote.
The decision module makes the path from question to consequence visible. Rather than starting with a voting interface, the system begins with the lifecycle of a decision.
Signal
Proposal
Deliberation
Decision
Effect / record
Design governance as infrastructure, not ceremony.
Local rules, shared grammar
Different spaces can govern differently while remaining understandable through the same product structure.
Membership is a relationship
Joining a space creates rights, obligations, permissions, and access — not just a user record.
Treasury follows authority
Resource movement should be legible in relation to who can decide, under which agreement, and on behalf of which space.
Exit is part of governance
A system is incomplete if it explains how people join and decide but not how responsibilities and permissions end.
Add the strongest UI / prototype showing:
agreements · members · treasury · child spaces
Proposal → context → authority → decision → record
Translate governance language into product entities.
A key design move was making the organizational model concrete enough to become software. The conceptual product model can be expressed through a small set of related entities.
The product became a grammar for composing governance.
The value of the model was not a single governance recipe. It was the ability to compose different governance contexts from the same understandable primitives.
The fractal structure creates a bridge between autonomy and coherence: each space can remain locally specific while still fitting into a larger system that people can navigate and understand.
The broader lesson for my product practice was that complex organizational behavior becomes designable when hidden relationships — membership, authority, resources, commitments, transitions — become explicit product objects.