> ## Documentation Index
> Fetch the complete documentation index at: https://docs.digitalasset.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Role Architecture & Asset Model

> A comprehensive guide to the primary roles, infrastructural hierarchy, and asset modeling within the DA Registry.

The DA Registry is built around a clear separation of concerns, dividing infrastructure management from asset lifecycle management, and asset definitions from individual ownership records.

## Role Architecture

The platform utilizes two primary administrative roles to ensure infrastructure sharing while maintaining strict organizational boundaries.

<CardGroup cols={2}>
  <Card title="Provider" icon="server">
    Operates the underlying DA Registry infrastructure. Providers are responsible for onboarding participants to the application and managing infrastructure-level access to DA Registry services.
  </Card>

  <Card title="Registrar" icon="building-columns">
    Creates and administers instruments on the DA Registry. Registrars handle the core asset lifecycle, including minting, burning, transfer controls, allowlists, and blocklists.
  </Card>
</CardGroup>

<Note>
  In token-standard terminology, the **registrar** acts as the definitive token administrator for a specific instrument.
</Note>

This role separation allows issuers, custodians, and tokenization platforms to operate dedicated registrar parties while securely leveraging a shared provider infrastructure. A single provider can support multiple registrars, and each registrar can administer one or more instruments.

### Infrastructure Hierarchy

```mermaid theme={null}
graph TD
    P[Provider] --> RA[Registrar A]
    P --> RB[Registrar B]
    
    RA --> I1[Instrument 1]
    RA --> I2[Instrument 2]
    RA --> I3[Instrument 3]
    
    RB --> I4[Instrument 4]
    RB --> I5[Instrument 5]
```

## Asset Model

The DA Registry implements the asset model defined in the [CIP-56 Canton Network Token Standard](https://docs.canton.network/overview/reference/cip-0056#cip-0056-canton-network-token-standard). This model splits the concept of an asset into two distinct layers:

This structural separation allows a single instrument definition to be globally referenced across multiple unique holdings, keeping asset administration, compliance controls, and actual ownership records independent.

### Instrument to Holding Relationship

```mermaid theme={null}
graph TD
    I[Instrument] --> HA[Holding A<br/>100 units]
    I --> HB[Holding B<br/>500 units]
    I --> HC[Holding C<br/>1,000 units]
```