All field guides

Constraint Alpha · Worked tool example

NVIDIA: Data Center Revenue Is Not Humanoid Revenue

Use a disclosed revenue category without turning it into an unsupported pure-theme estimate.

Published October 4, 2026 · Agent-assisted source review; human review not claimed.

Start with the scope of the question

A reader asks: “NVIDIA is involved in humanoid robotics. How much of its revenue comes from humanoids?” A product announcement establishes involvement. It does not supply the numerator for a revenue-share calculation.

This example separates two questions: the share of revenue in a reported market category, and the share attributable to a narrower investment theme. Keep those questions separate when screening suppliers.

Reported facts and a reproducible calculation

For Q2 FY2027, ended July 26, 2026, NVIDIA reports total revenue of $96,221 million and Data Center revenue of $89,023 million. Dividing the latter by the former gives 92.52%. These are matching quarterly amounts in USD millions.

That result describes the reported Data Center category. It does not measure pure AI revenue, humanoid revenue or the economics of one named customer. The source tables do not separately quantify humanoid revenue. Our example therefore leaves that field blank.

Sources: NVIDIA Q2 FY2027 Form 10-Q, revenue by specialized market, filed August 27, 2026; results release, August 26, 2026. Checked October 4, 2026.

Try both questions in the worksheet

  1. Open the tool and select Load example. It fills total revenue and the source, leaving humanoid revenue unknown.
  2. Select Calculate / inspect. The output should say Unknown, rather than 0%.
  3. For the separate category question, rename the scope to “Data Center — reported category” and enter 89,023. Calculate again to reproduce 92.52%.

Open Revenue Exposure Checker →

Make the unknown useful

Record what disclosure would resolve the question: a product revenue breakdown, a separately quantified contract, or a management statement defining the category. Revisit that request at the next reporting date. Do not assign broad revenue to a narrow theme merely because the technologies overlap.

The relationship selector is a research note, not a verification engine. Its default in this example is Not verified because no particular customer contract is being evaluated. Edit it only when your own source supports a specific relationship.

This is a dated educational example, not a forecast or an investment recommendation. See the relationship and exposure framework for the next evidence checks.