"EDV Microkernel" Architecture: C-callable "kernel" on which everything else is implemented (i.e. all of the services)

Consider the "C-callable" API I've mentioned in the Related Issues (see below) as the "kernel" for a Layer A data vault ... like an operating system kernel ...the EDV Kernel ...or EDV Microkernel (if you want a sexier name).

**EDV Microkernel**
- Includes all of the functions necessary to manage and manipulate and manage an EDV data vault and its content.

**Services Built on Top of the EDV Microkernel**
- EDV Data Vault Management - CRUD operations to manage the creation, deletion of individual data vaults
- EDV Data Vault Content Management - CRUDPlus4 operations on content stored in a data vault
- Content Replication: Outbound Processing, Package Transfer, Inbound Processing
- Content Indexing
- Search Query Processing
- etc.
- etc.

Related issues:

- https://github.com/decentralized-identity/confidential-storage/issues/167
- https://github.com/decentralized-identity/confidential-storage/issues/179
- https://github.com/decentralized-identity/confidential-storage/issues/180