mokunet
How it works

Every feature resolves to a place

A spatial backbone built from 18 authoritative datasets anchors all governance — projects, programs, research, and compliance — to Hawai'i's 33 traditional moku. What you can see, do, and contribute depends on your role and where you work.

Three layers

Data flows from authoritative spatial sources, through role-scoped access, to community-contributed observations.

Layer 1Spatial Backbone

18 authoritative datasets, one read-only spatial model
The foundation is a spatial dataset assembled from 18 state and federal sources — moku boundaries, agricultural land, conservation reserves, wetlands, schools, highways, and more. Every zone is geocoded and linked to one of 33 moku districts. The backbone is immutable: the platform reads it but never writes spatial data.

Layer 2Role-Based Perspectives

Your profile and moku determine what you see
When you subscribe, a short interview assigns your profile type based on your primary work. Combined with your moku affiliation, this determines which zones, features, and governance relationships are relevant to you. Two people in the same system see different things because the backbone scopes what each role can act on.

Layer 3Observations & Indicators

Community-sourced data the backbone alone cannot provide
Observations are geocoded environmental samples (water quality, soil tests, species surveys) contributed through the Research Commons. Indicators are sub-county statistics that refine county-level federal baselines. Both are spatially resolved to the backbone — neither modifies it.

By the numbers

33
Moku districts
19,720
Backbone cells (res-8)
40,000+
Zone overlays
9
SDG goals

Current platform status

Mokunet is under active development — here is what is live today and what is coming next.

Live

  • Spatial backbone (33 moku, 18 datasets)
  • Unified project system (6 types, lifecycle stages)
  • Subscriber onboarding with role + moku assignment
  • Producer sync from bGoodFarms
  • IDS Editor with project persistence
  • Research Commons ingestion pipeline

In progress

  • Subscriber registry (your projects, roles, affiliations)
  • Monitoring network aggregation
  • Observations warehouse for sample storage
  • External API for partners and developers
  • Lifecycle assessment data

Explore further

Standards & specifications

The ISO, buildingSMART, and GS1 standards Mokunet builds on, and how they route toward the SDGs.

Facility IDS

How a building model's data requirements get tied to the contract, moku, and place that govern it.

Island baselines

Federal statistics mapped onto the moku backbone — and why their SDG alignment stays editorial until research grounds it.

Supply chain governance

District-anchored projects from planning through operations, with contract evidence and provenance.

The onboarding agent

How a guided agent interview sets up each subscriber and advocates for their moku.

Roles & perspectives

The professional profile types and the public roles each unlocks.
Why moku?Join the network