The AltVaults Vault Spec: From Legal Documents to Operational Data

Authoritative versus operable

Legal documents are authoritative and they are poor software interfaces. A 140-page limited partnership agreement does not tell an onboarding system whether this investor may subscribe, or tell a reporting job when the next valuation is due.

The Vault Spec extracts the operational facts — without pretending to replace counsel. If the document and the spec disagree, the document wins, and the spec is versioned to catch up.

Five layers, one record

Legal and governance. Investment mandate. Investor eligibility. Capital and lifecycle. Reporting and risk. Those five categories are enough to configure a private-credit product, a real-estate debt book or a fund-of-funds sleeve without inventing a new schema each time.

A small, explicit model beats a flexible one that nobody can audit. Version control matters: a change to a redemption notice should be an event, not a silent edit.

If it changes the investor’s rights or the operator’s duties, it is a version, not a setting.

Built to be integrated

Administrators, verification providers and wealth platforms should be able to read the same spec. That is the interoperability private markets actually need: not a universal token, a universal description of the product.

The sample schemas published with AltVaults are illustrative. They are not an offer, and they are not legal advice. They show the shape of the operating layer.