When the oracle goes quiet: a stale NAV is not a NAV
AI Compute Basket is showing a stale price feed. Here is why the honest answer is a warning label, not a hidden refresh.
· 5 min read · robindaos.fun editorial
Figures cited in this paper
- Reported NAV (point in time)
- 512,000 USDG (1.12 per share)
- Liquid NAV (point in time)
- 450,000 USDG (0.98 per share)
- Liquid coverage (point in time)
- 88%
- Oracle staleness (point in time)
- 95 minutes since last update
- Data confidence (point in time)
- 0.60
- TWR / max drawdown (7d)
- -2.1% / -6.0%
Paper Competition (Season 0). Source: Season 0 paper fixtures, as of . No user funds are accepted; nothing here is investment advice.
What happened
AI Compute Basket, Ana Vasquez's strategy for the compute and infrastructure layer of the AI buildout, is currently flagged with a stale oracle. At the figures date the last price update was 95 minutes old, so every NAV number on the page is a snapshot of the past, not the present.
The surface does not pretend otherwise. The strategy page shows the stale flag, drops its confidence badge to 0.60, and keeps the timestamp of the last good update visible. Over the trailing 7 days the strategy printed a -2.1% TWR with a -6.0% max drawdown in the same window, and both of those numbers inherit the same staleness caveat.
Why we show stale instead of hiding it
The tempting move is to keep rendering the last known NAV as if it were live. That is how NAV decoupling starts: the screen says one number, the market says another, and the gap surfaces at the worst possible moment, usually redemption.
Every financial snapshot here carries its provenance: an as-of timestamp, a source, a confidence value, a coverage percent and a stale flag. When the oracle stops, the metadata says so, and the UI is obligated to render it. A stale NAV is information about the past; treating it as the present is fabrication.
Reported versus liquid, again
Staleness also compounds the difference between the value layers. Reported NAV values the book at supported prices: 512,000 USDG, or 1.12 per share. Liquid NAV asks what could actually be exited under defined slippage and depth: 450,000 USDG, or 0.98 per share, with 88% of value covered by supported prices and real liquidity.
When prices are 95 minutes old, the reported number is the more fragile of the two. Depth aware haircuts age better than point prices, but neither should be read as fresh until the oracle resumes.
How to read a stale surface
Practically: trust the timestamp over the number, prefer liquid NAV over reported NAV, and treat any decision as deferred until the feed recovers. The stale state is temporary by design; the strategy keeps trading inside its policy and the page recovers on the next oracle update.
Season 0 runs on paper fixtures, which is exactly why this state is on display. The product is built against difficult states first, so a stale oracle in a live phase will look boring instead of alarming.