Getting started / Overview

# Preview the muniment setup flow

This page previews the intended setup flow. Muniment is not yet generally available, so public visitors cannot create an org, use the admin console, connect identity, download apps, or run a route today.

## Org foundation

The intended flow begins with an owner establishing the organization that people will recognize in the apps. That organization will hold policy, gateway, and audit settings in one administrative boundary.

## Identity model

The planned identity layer uses SSO and SCIM so directory groups can become the basis for entitlements, routing grants, and audit context.

identity settings

```
identity source   organization directory
provisioning      SSO + SCIM
policy context    synced groups
```

## Access model

In the intended model, owners grant capabilities through synced groups and use explicit denies for roles that should never reach a route. A capability is the end-user grant target; its skills, extensions, connections, workflows, and model requirements are reviewed together and are never granted independently.

## One primitive: the capability

Everyone else ships four loose nouns: connectors, skills, plugins, and workflows. Muniment ships one governed unit that an organization reviews, grants, meters, and sees in every receipt.

Each signed, versioned capability can contain skills, extensions, connections, workflows, and model requirements. Connections bind by name to approved entries in the MCP registry or local-stdio allowlist. Those registries are substrate: they own endpoints and authentication while capabilities define the reviewed tool surface.

Grants follow a channel and are gated when that surface changes. Content-only updates can flow on the approved channel; an update that adds a connection, extension, hook, model requirement, or scope waits for review while grantees remain on the last approved version. You granted a shape, not a snapshot — when the shape grows, we ask again.

## App distribution

Once released, the desktop app, mobile companion, browser capability, Muniment CLI, and VS Code companion will sign in to the organization while provider credentials remain behind the gateway instead of landing on user devices. These surfaces are not available during preview.

At general availability, macOS builds will be Developer ID-signed and notarized. During preview, an unsigned build's first launch requires right-clicking the app and choosing Open, or removing its quarantine attribute before launch.

## Policy route

The intended result of setup is a request handled by an owner-defined route. A provenance line will name the matched route, model, cost, time, and every capability and version in the loop so the user can verify that policy handled the request.

research-default · model-pro · $0.018 · 2.4s · research@1.4.2

## What comes next

Detailed procedures will appear only as their corresponding product surfaces become available. For now, use this sequence to evaluate the intended relationship between identity, policy, apps, and receipts.

-   Desktop app install soon
-   Mobile companion soon
-   Browser capability soon
-   Muniment CLI soon
-   VS Code companion soon
-   Identity & SCIM soon
-   Routing soon
-   Org model endpoints soon