Role-Based Perspectives

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.

How Profile Assignment Works

The interview asks about your primary work — not your job title. 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.

After assignment, your profile type and public role are locked. This prevents role drift and ensures that governance scoping remains consistent. If your work changes, you can request a profile change through a formal process.

Profile Types

Each profile type maps to specific spatial constraints and feature scopes:

| Profile Type | Spatial Focus | What You See | |------------------------------|---------------------------------------------------|-----------------------------------------------------------| | Planning Professional | Zoning districts, IAL dockets, dev standards | Site feasibility, regulatory compliance, density analysis | | Design Manager | Project locations, specification zones | Design coordination, IDS documents, system integration | | Facilities Support | Facility locations, infrastructure zones | Work orders, maintenance logs, condition reporting | | Hub Manager | Green Fee project sites, program districts | Project pipeline, SDG alignment, funding, impact metrics | | Institutional Procurement| Producer locations, supply chain zones | Producer onboarding, GAP/CNP compliance, product catalog | | Land Asset Manager | Steward parcels, conservation reserves, ag land | Stewardship reporting, ecosystem assessment, land condition| | Administrator | All zones, all districts | System health, data sync, governance metrics |

What "Spatial Focus" Means

A Hub Manager in Koolaupoko and a Land Asset Manager in Kona both access the same backbone, but the system filters what is relevant to each. The Hub Manager sees Green Fee project sites, program districts, and SDG alignment metrics for their moku. The Land Asset Manager sees steward parcels, conservation reserves, and agricultural land classifications for theirs.

This is not a permissions model — it is a relevance model. The backbone contains everything; your profile type determines which layers matter to your work.

Projects and Lifecycle

All profile types can create and manage governed projects. There are six project types, each following the same four-stage lifecycle:

Project Types: Green Fee, Facilities, Location, Research, Infrastructure, Cooperative

Lifecycle Stages: Planning → Design → Construction → Operate

When you create a project, the system generates its identifier automatically based on your SDG alignment, moku affiliation, and project name. The identifier encodes provenance — from the ID alone, anyone can determine the goal area, district, and location context.

Projects are the primary unit of work in the system. They link to programs (SDG-aligned umbrellas), connect to moku districts through the backbone, and accumulate provenance through lifecycle stage progression.

Subscriber Registry

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 data internally. A subscriber-facing view where you can browse your own governance connections is under active development.