How it works
Skills are gated capabilities granted to a subscriber.
A skill is both an entitlement and a growth surface. It defines what the onboarding agent can do on your behalf — which data it may read or write, which workflows it may run — and it is always scoped, gated, and tied to a real professional role. This page explains the taxonomy conceptually; some pieces are built today and some are still in development.
What a skill is
Every skill in the catalog is a single record describing a capability the agent can exercise for you. Rather than handing every subscriber the same access, the platform grants narrow, auditable capabilities that match your work.
An entitlement
A skill names exactly what it unlocks — specific reads and writes against the graph, specific workflows, specific parts of the interface. Nothing is implicit.
Scoped, not blanket
Each grant carries a scope — the whole platform, a single moku, or one project — so a capability you hold in one district does not leak into another.
A vocabulary-growth surface
Using a skill can surface new terms the moku ontology should learn. Those proposals move through curation — proposed, then accepted, then merged — so the platform's shared vocabulary grows alongside the people using it.
Three scopes
Every grant answers a simple question: where does this capability apply? Scope is the difference between a platform-wide ability and one that is confined to a single district or project.
global
per-moku
per-project
global
Applies platform-wide. Reserved for capabilities that are not meaningfully tied to one place — for example, opting into platform stewardship.
per-moku
Confined to a single moku district. The agent reasons within that district's data and relationships, never across boundaries you were not granted.
per-project
The narrowest scope — one project. Useful for collaborators who need to act on a single initiative without broader access.
How onboarding unlocks a baseline skill
You do not start from zero, and you do not start with everything. Completing the onboarding interview is itself the unlock for a universal baseline entitlement — the prerequisite that other skills build on.
1
Complete onboarding
A short interview establishes your profile type, organization, and home moku.
2
Baseline skill granted
Finishing the interview is itself the unlock for a universal baseline entitlement.
3
Join as an early adopter
An opt-in adds you to platform stewardship — recorded as a signal tied to your moku.
4
Skills grow with you
Further capabilities are requested, scoped, and granted as workflows roll out.
In the current phase, every subscriber joins as an early adopter. Completing onboarding is the self-grant — there is one path for now. Your opt-in tells the platform that your home moku has a stakeholder willing to help surface where the shared vocabulary needs to grow, and that signal is recorded against your moku affiliation.
How a skill is granted
Grants are not all the same. A skill declares who may turn it on — and many capabilities are still being provisioned, so the catalog is honest about what is live versus planned.
Granted automatically
Some entitlements are conferred the moment a prerequisite is met — for example, the baseline skill that finishing onboarding confers.
Self-authority opt-in
Some skills you can request for yourself. Early-adopter participation is opt-in: any functional profile type can choose to join platform stewardship after onboarding.
Administrator-granted
Higher-trust capabilities are granted by an administrator, keeping sensitive write access deliberate and reviewable.
Provisioning status:plannedin provisioningenabled
A skill in the catalog is not necessarily a skill you can use today. Each entry carries a status — planned, in provisioning, or enabled — so the platform never promises a capability before it is actually wired up. Most of the catalog beyond the baseline is still in development.
Skills map to profile types
Capabilities follow expertise. A skill declares which professional profile types it is for, so data-governance permissions line up with real-world responsibility — the same principle behind the role system.
Profile type gates access
Subscribers are assigned a profile type based on their work — planning professional, design manager, facilities support, hub manager, institutional procurement, land asset manager, or administrator. A skill is only offered to the types it lists.
Collaborative by design
When two people work on the same project, contract, program, or moku, the agent can surface that overlap — so capabilities support coordination rather than siloing each subscriber.
Skills extend the moku ontology
The moku ontology is evolving incrementally, and subscriber actions are the mechanism. Each skill declares which branches of that ontology its actions can extend — keeping growth organized rather than ad hoc.
Spatial
Governance
Design
Production
Environment
Institutional
Community
Systems
Most branches grow district-domain vocabulary — spatial, governance, design, production, environment, institutional, and community knowledge about the moku themselves. The systemsbranch is different: it covers platform stewardship — registry validation, vocabulary curation, and drift detection — and is gated behind early-adopter participation. Its findings feed the platform's existing learning layer rather than a parallel one. These systems-stewardship workflows are still in development.
Built versus planned
Built today
The skill catalog's shape, the early-adopter baseline, scope and grant-authority rules, the onboarding interview that establishes your profile type and home moku, and the early-adopter framing across the subscriber experience.
In development
The full set of per-role skills, the conversational onboarding agent, agent-driven reads and writes through audited services, vocabulary curation, and the systems-stewardship workflows. These are designed and scaffolded, not yet shipped.
Skills are how Mokunet keeps an evolving platform honest: every capability is named, scoped to a place, matched to a role, and marked for what is actually live. As workflows roll out, your skills grow with you.