Your moku, your kuleana

Two people, one system, different views.

When you join Mokunet, a short onboarding conversation sets your role based on the work you do. Together with your moku, that shapes which places, features, and connections the system shows you. The shared map holds everything — your role decides which parts matter to you.

See the full role breakdown Start with the shared map

The shape of role-based perspectives

A handful of structural facts define how access is scoped. Profile type and moku together frame what you act on; projects and SDG goals give that work a shared vocabulary across the state.

Profile Types

Project Types

Lifecycle Stages

SDG Goals

It's about relevance, not permission

Consider a Hub Manager in Koʻolaupoko and a Land Asset Manager in Kona. Both reach the same read-only map, but the system shows each of them what's relevant.

Hub Manager in Koʻolaupoko

Sees Green Fee project sites, program districts, and SDG-impact measures for their moku — the flow of funded work they coordinate.

Land Asset Manager in Kona

Sees steward parcels, conservation reserves, and agricultural land classifications for theirs — the condition of the land they steward.

This is not a permissions wall. The map holds everything; your role brings the parts that matter into focus. Same data, different view — shaped by where you work and what you do.

The same work, a shared vocabulary

Whatever your profile, the unit of work is the same. All profile types create and manage governed projects — six types, each following the same four-stage lifecycle.

Project types:Green FeeFacilitiesLocationResearchInfrastructureCooperative

Planning

Scope the work, align to an SDG goal, and anchor it to a moku.

Design

Coordinate specifications and digital models for what will be built.

Construction

Track what is actually built against what was planned.

Operate

Run, maintain, and measure the project's ongoing impact.

Every project carries its story

When you create a project, the system gives it a name built from your SDG goal, your moku, and the project name. From that name alone, anyone can read the goal, the district, and the place — so every project connects back to the shared map and builds a record as it moves from planning to outcome.

A view of your own connections

Behind the scenes, joining creates a record of your connections — your moku, any projects you create, and any steward roles you hold. The platform already tracks this internally. A view where you can browse your own connections is being built.

Browse all six profiles

Want the per-role detail? The full breakdown of all six roles — what each one focuses on, exactly what it sees, and how a role is set and locked — lives at /roles. This page covers the core idea; that page covers every role.