Community governance
Participation, scoped to expertise
Mokunet organizes community participation around six professional profile types. When you subscribe, a brief onboarding interview determines your profile type based on your primary work — not self-selection. This deterministic approach ensures each subscriber's registry permissions and data governance scope match their actual domain of practice.
Once set, your profile type is locked for governance integrity. Each type unlocks specific public roles, dashboard sections, and registry actions — so the data endpoints in each moku are managed by subscribers with the relevant domain expertise.
Subscriber registry & shared responsibility
Registry model
Each subscriber has a registry record tracking three dimensions of participation: projects you've registered, stewardships you hold across moku districts, and affiliations connecting you to the governance relationships in your area.
Shared responsibility
The platform provides governance scaffolding — spatial backbone, lifecycle stages, compliance frameworks — while subscribers own their data. Your registry defines what you govern; the backbone ensures contributions are traceable and domain-appropriate.
Looking ahead: the subscriber registry is designed so each participant can eventually manage their own data and workflows within the governance framework — owning their contributions while the backbone maintains traceability across districts.
Connected to a wider network
Partner organizations — community apps, producer platforms, research portals, and public dashboards — connect to Mokunet through authorized API endpoints, each scoped to its domain.