Private credit, on one operating system

Covenants are continuous, not quarterly. Financial covenants, leverage tests, liquidity floors and reporting covenants must be tracked on the cadence the credit agreement specifies, not when someone remembers to check the spreadsheet.

NAV facilities and subscription lines need their own waterfall. Drawn, undrawn, accrued interest, mandatory prepayments and recyclability all sit in different ledgers in most funds. They need to live together.

Workout situations require institutional memory. When a borrower trips a covenant the diligence done at origination, every consent and waiver since, and every conversation with the sponsor matters. Spreadsheets lose that history.

LPs in credit want different reports. Yield, loss given default, weighted average life, current pay vs PIK, and concentration by industry and seniority. Equity-style LP reports do not answer the question.

Private Credit carries 18 sub-asset overlays in the Reuben AI rubric registry: Direct lending unitranche, Senior secured, Second lien, Unitranche with equity kicker, NAV lending, GP financing, Fund finance and subscription lines, Specialty finance, Consumer lending, SME lending, Revenue based finance, Equipment finance, Aviation finance, Shipping finance, Litigation-backed lending, Royalty-backed lending, Carry advance and Option exercise financing. 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 direct lending unitranche deal and a option exercise financing deal are both scored on the shared private Credit 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 private Credit book has accepted. Nothing is retrofitted later by hand.

Every private Credit 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 private Credit position was underwritten the way it was, the answer is retrieved, not reconstructed.

Private Credit sits as a core allocation for Private Credit and Institutional mandates, and is adjacent or opportunistic for 5 of the other fund types the platform serves.

That matters operationally because most funds do not hold private Credit alone. The moment a portfolio spans more than one asset class, comparability becomes the constraint: a position scored on a bespoke private Credit spreadsheet cannot be ranked against a position scored somewhere else. Running private Credit 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 private Credit position appears in the quarterly pack on the same basis as every other holding, with the same evidence behind it.