Repositories Data Dictionary (Beta)

Purpose: Facilitates exchange, storage, or sharing of the Source and Deposits data. May represent external data registries, transaction/delivery, or verification workflow.

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