# Repositories Data Dictionary (Beta)

<table data-header-hidden><thead><tr><th width="165"></th><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Field</strong></td><td><strong>Data Type</strong></td><td><strong>Description</strong></td><td><strong>Example</strong></td><td><strong>Constraints / Notes</strong></td></tr><tr><td><strong>Repo ID</strong></td><td>String / UUID</td><td>A unique identifier for the Repository record.</td><td><code>REPO-789456</code></td><td>Primary key for the repository; must be unique.</td></tr><tr><td><strong>Custodian ID</strong></td><td>String / UUID</td><td>Identifies the entity/account responsible for this repository.</td><td><code>CUST-001</code></td><td>Maps to an internal or external “custodian” entity.</td></tr><tr><td><strong>Type/s of Repo</strong></td><td>String (enum/set)</td><td>Indicates the repository’s use-cases (e.g., Verification, Transaction, Audit).</td><td><code>["Verification","Audit"]</code></td><td>Could be a list/array if multiple roles apply.</td></tr><tr><td><strong>Counterparty ID</strong></td><td>String / UUID</td><td>Identifier for additional party(ies) involved (custodian, verifier, owner, auditor).</td><td><code>USER-12345</code></td><td>May need multiple references if multiple parties exist.</td></tr><tr><td><strong>Counterparty Role</strong></td><td>String (enum)</td><td>The specific role(s) the counterparty plays in this repository (e.g., verifier, auditor).</td><td><code>verifier</code></td><td>Could be “custodian,” “verifier,” “owner,” or “auditor.”</td></tr><tr><td><strong>Counterparty Permissions</strong></td><td>String (enum)</td><td>Level of access granted (e.g., read, write, verify).</td><td><code>read, verify</code></td><td>Reflects the system’s access control model.</td></tr><tr><td><strong>Counterparty Email</strong></td><td>String (email format)</td><td>Contact email address for the counterparty.</td><td><code>verifier@example.com</code></td><td>Optional but useful for notifications.</td></tr><tr><td><strong>Transaction/Contract ID</strong></td><td>String / UUID</td><td>Identifier for transactions or contracts relevant to this repository.</td><td><code>TX-000999</code></td><td>Could link to a separate ledger or contract management system.</td></tr><tr><td><strong>Volume/Quantity → Deposits</strong></td><td>Array of Deposit IDs</td><td>References to Deposit ID(s) stored/transacted in this repository.</td><td><code>["DEP-456789","DEP-1122"]</code></td><td>Must match existing Deposit records.</td></tr><tr><td><strong>Volume/Quantity → SSIDs</strong></td><td>Array of Source SSIDs</td><td>References to Source SSIDs relevant to the deposits or data in this repository.</td><td><code>["SRC-000123","SRC-005"]</code></td><td>Must match existing Source records.</td></tr><tr><td><strong>Settlement Info → Price</strong></td><td>Decimal / Float</td><td>Monetary amount or price for a transaction in the repository.</td><td><code>1000.00</code></td><td>Could store currency code separately (e.g., “USD 1000.00”).</td></tr><tr><td><strong>Settlement Info → Method</strong></td><td>String (enum)</td><td>How payment or settlement is conducted (e.g., “cash,” “token,” “credit”).</td><td><code>token</code></td><td>Could reflect fiat, on-chain tokens, or other payment methods.</td></tr><tr><td><strong>Access Controls &#x26; Encryption Keys</strong></td><td>String / Object</td><td>Security fields for read/write or cryptographic permissions.</td><td>JSON object of key data</td><td>May store references to actual public keys or hashed credentials.</td></tr><tr><td><strong>Audit Logs</strong></td><td>Array / Log object</td><td>Record of actions/events performed in the repository (access, edits, verifications).</td><td><code>[{"action":"create",...}]</code></td><td>Could be stored as a structured log with timestamps, user IDs, etc.</td></tr></tbody></table>