Layer 2 of how Mokunet works

Two people, one system, different views.

When you subscribe to Mokunet, a short onboarding interview assigns your profile type based on your primary work. Combined with your moku affiliation, this determines which zones, features, and governance relationships the system surfaces for you. The spatial backbone contains everything — your role decides which layers matter to you.

See the full role breakdown Start with the backbone

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

A relevance model, not a permissions model

Consider a Hub Manager in Koolaupoko and a Land Asset Manager in Kona. Both reach the same read-only backbone, but the system filters what is relevant to each.

Hub Manager in Koolaupoko

Sees Green Fee project sites, program districts, and SDG alignment metrics for their moku — the pipeline 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 backbone holds everything; your profile type determines which layers come into focus. Same data, different perspective — scoped by where you work and what you do.

How your profile is assigned

The interview asks about your primary work — not your job title.

Derived, not selected

A deterministic mapping converts your answer to one of seven profile types. There is no role-selection menu and no guesswork: the system derives your profile from what you do.

Locked after setup

Once assigned, your profile type and public role are locked to keep governance scoping consistent and prevent role drift. If your work changes, you can request a profile change through a formal process.

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.

Identifiers carry provenance

When you create a project, the system generates its identifier automatically from your SDG alignment, moku affiliation, and project name. From the ID alone, anyone can read the goal area, district, and location context — so every project connects back to the backbone and accumulates a record as it moves through its lifecycle.

A view of your own connections

Behind the scenes, your subscription creates a record of your governance relationships — your moku affiliation, any projects you create, and any steward roles you hold. The platform already tracks this internally. A subscriber-facing view where you can browse your own governance connections is under active development.

Browse all seven profiles Meet the onboarding agent

Want the per-role detail? The full breakdown of all seven profile types — their spatial focus and exactly what each one sees — lives at /roles. This page covers the core idea; that page covers every role.