> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.clossir.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.clossir.com/_mcp/server.

# Concepts

GETTING STARTED · CONCEPTS

Clossir has five core concepts. Understanding how they compose is the key to integrating
effectively.

## Organizations

An **organization** is the top-level tenant. Every resource — parties, assets, keys, policies —
belongs to exactly one org. API keys are org-scoped, and Row-Level Security ensures complete
data isolation between orgs.

Organizations operate in either `testnet` or `mainnet` network mode. Testnet is the default;
mainnet requires explicit opt-in.

## Attestations

An **attestation** is a cryptographic claim about a party or wallet — "this entity is KYC'd",
"this wallet belongs to an accredited investor", "this address passed sanctions screening."

Attestations are:

* **On-chain** — settled as verifiable credentials on the target blockchain
* **Portable** — a single attestation can be bridged across chains via LayerZero
* **Composable** — compliance policies reference attestation types as prerequisites

The lifecycle: `create` (command, `POST → 202`) → processing (async) → settled (on-chain,
queryable via `GET → 200`).

## Policies

A **policy** defines the rules an asset enforces on every transfer. Policies are declarative:
you specify *what* must be true (e.g. "both parties hold an `accredited_investor` attestation"),
and the on-chain contracts enforce it automatically.

Policies compose attestation types into transfer rules — connecting Identity to Compliance to
Asset Issuance.

## Assets

An **asset** is a tokenized real-world instrument — an equity share, a fund unit, a bond. Each
asset is deployed as a smart contract on one or more chains, governed by its compliance policy.

Assets support:

* **Issuance** — deploy the token contract and mint to eligible holders
* **NAV & distributions** — settle net asset value and distribute yield
* **Fees** — protocol and issuer fee schedules, with fee-sharing for platforms

## Webhooks

Commands are processed **asynchronously**. Once a command settles, the platform notifies your
systems via **webhooks** with typed payloads. Webhooks drive:

* **On-chain settlement** — commands are picked up and settled on-chain in the background
* **State sync** — the read database updates when chain transactions confirm
* **Notifications** — your systems are notified via webhooks when state changes

You never need to parse anything raw — the SDK and webhooks deliver typed payloads. See the
[API Reference](/api/overview) for the webhook payload schemas.

## How they compose

```
Organization
  └─ Parties (verified via Identity)
       └─ Attestations (on-chain claims)
            └─ Policies (reference attestation types)
                 └─ Assets (enforce policies on transfer)
                      └─ Webhooks (async delivery)
```

Identity feeds Compliance, which gates Asset Issuance. Every layer is accessible through the
same API key, scoped to your org.

## Next steps

* [Authentication](/getting-started/authentication) — understand API keys and permission scopes
* [Identity](/products/identity/overview) — deep-dive into parties and attestations
* [Compliance](/products/compliance/overview) — policy authoring and enforcement