Digital Assets, with structure-aware discipline

Custody is fragmented. Positions sit across qualified custodians, exchanges and cold wallets. Reconciliation needs to be continuous and provable to auditors.

SAFTs and vesting matter. Locked and unlocking positions represent significant NAV. Vesting schedules and cliff dates need structured tracking.

Staking creates yield and risk. Staked positions generate yield but carry slashing and unbonding risk. Both sides need to be tracked and reported.

Regulation is jurisdiction-specific. MiCA in the EU, MAS in Singapore, SEC guidance in the US and evolving frameworks elsewhere each impose different reporting and custody standards.

Digital Assets carries 7 sub-asset overlays in the Reuben AI rubric registry: Liquid token, Venture token, Staking and validation, Market making, DeFi protocol lending, Real world asset tokenisation and Custody and infrastructure. Those overlays are part of the 314 sub-asset overlays the platform maintains across 56 of its 68 native asset classes.

An overlay never reweights the parent rubric. It adds the extra scoring criteria, risk flags, document types and key term fields that only apply to that slice, so a liquid token deal and a custody and infrastructure deal are both scored on the shared digital Assets rubric while each is still asked the questions specific to its structure. That is what keeps deals inside one asset class comparable to each other and to the rest of the portfolio.

Selecting an overlay at intake changes what the platform expects: the document checklist, the extraction schema for key terms, and the flags raised when a term sits outside the range the rest of your digital Assets book has accepted. Nothing is retrofitted later by hand.

Every digital Assets opportunity that moves through Reuben AI leaves a structured record rather than a folder of documents and a memo. The rubric score is stored with the criteria that produced it, each extracted key term is stored with the clause and page it came from, and every flag is stored with the reason it fired and who cleared it.

The practical effect is that the investment committee paper, the LP report line and the audit trail are all reading the same underlying record. When an LP asks in year three why a digital Assets position was underwritten the way it was, the answer is retrieved, not reconstructed.

Digital Assets is a specialist allocation rather than a core one, relevant to VC and Hedge Fund mandates and held opportunistically elsewhere.

That matters operationally because most funds do not hold digital Assets alone. The moment a portfolio spans more than one asset class, comparability becomes the constraint: a position scored on a bespoke digital Assets spreadsheet cannot be ranked against a position scored somewhere else. Running digital Assets on the same rubric engine as the rest of the book removes that break.

Reporting inherits the same property. Portfolio monitoring, valuation cadence, capital account movement and LP reporting all draw from the single stored record, so a digital Assets position appears in the quarterly pack on the same basis as every other holding, with the same evidence behind it.