Community Governance
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 description — not self-selection. This deterministic approach ensures that 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. This is how the platform ensures that data endpoints are managed by subscribers with the relevant domain expertise.
Profile Types
Your profile type is determined by your primary work area during onboarding.
Planning Professional
Help plan land use and development in your district. Analyze sites, check zoning rules, and guide sustainable growth.
Design Manager
Oversee design work and project deliverables. Track specifications, coordinate teams, and integrate with partner organizations.
Facilities Support
Keep community facilities running. Create work orders, track maintenance, and report on infrastructure conditions.
Hub Manager
Run the Green Fee project pipeline. Review proposals, track funding, and measure community impact aligned with Sustainable Development Goals.
Institutional Procurement
Bring local producers onboard, verify product compliance, and map supply chains. Connects to bGoodFarms.
Land Asset Manager
Manage land resources and conservation efforts. Track ecosystem health and coordinate stewardship across districts.
Subscriber Registry & Shared Responsibility
Registry Model
Each subscriber is provisioned as a User node in the governance graph. Your manifest tracks three dimensions of participation: projects you've registered, stewardships you hold across moku districts, and sessions representing your active engagement with the platform.
Shared Responsibility
The platform provides governance scaffolding — spatial graph, lifecycle stages, compliance frameworks — while subscribers own their data endpoints. Registry endpoints define what each subscriber governs; the governance graph ensures that contributions are traceable and domain-appropriate.
Research direction: Container orchestration for subscriber-provisioned resources — where each participant manages their own data and workflow endpoints within the governance framework. This is an active research concept informed by the platform's subscriber registry architecture.
External Data Orchestration and Graph Support
Partner organizations query MokuNet namespaces through CORS-authorized REST endpoints. The typed contract at mokunet-api-spec.ts defines the integration surface — 10 endpoints across 4 backend systems, importable as TypeScript types.
Community kuleana app — island-scoped queries across all pillars
kuleana.ainadesign.orgProducer onboarding and farm web map features
bgoodfarms.comUniversity and community research data — map views, contributions, and programmatic API access for UH/HPU labs
huikoeaina.ainadesign.orgAggregated metrics by island, district, program, and SDG
Public endpointsIFC model design sandbox — single-source data objects for IDS specification workflows
mokulab.io