A NAV you can defend in committee

Every instrument that references private-market value inherits a hard question: where does the number come from, and why should anyone believe it? For institutional allocators, that question is not rhetorical. It is the first hour of diligence, and it decides whether the second hour happens.

Much of the on-chain world has answered it casually — a single feed, an opaque update process, a methodology that lives in a forum post. That may be tolerable for speculative products. It is not tolerable for an instrument that an investment committee has to stand behind, report on, and explain to its own oversight functions.

Methodology first, number second

EquiTrack is being built in the opposite order. Each basket starts from a written, versioned methodology: what qualifies for inclusion, what does not, how reference values are derived, how often they update, and what happens when inputs disagree or go stale. The number is an output of the document — never the other way round.

On the data side, we are designing reference values to draw on multiple independent sources rather than a single feed, with deviation monitoring between them and circuit breakers that pause activity when inputs fall outside defined tolerances. The honest position on private-market data is that it is imperfect; the institutional answer is to be explicit about cadence, tolerance and tracking limitations, and to halt rather than guess when those limits are breached.

Reporting is part of the product

A defensible value also has to arrive in a defensible format. We treat reporting as a core product surface: exposure, composition, methodology version and control state, delivered in a form a committee can actually consume. If a risk team cannot reconstruct how we got to a number, we have not finished building it.

None of this is the fast way to ship. It is the only way to ship something institutions can hold.