The portfolio
61 products as a customer meets them — purpose, audience, revenue model and BB2G's own monetization score. It scores every row as though the row existed.
The part most decks leave out
Three registries.
They do not agree.
Every disagreement below was found by joining the sources rather than by choosing between them. None has been smoothed. Smoothing them is the thing that would cost this package its credibility.
The sources
What is being reconciled.
The order of battle
72 rows as an engineer meets them — tier, priority, IP status, ceiling, and a measured build state for each.
The live fleet
438 candidate addresses probed over HTTPS at build time; 423 answered. Captured with each page's own served title, so a mapping can be judged instead of asserted.
Printed, not smoothed
4 disagreements.
How many products are there?
One source says61 (portfolio.json, the market view)
The other says72 (order of battle, the engine view)
Neither is wrong. They are different cuts — one lists what a customer buys, the other lists what has to be built. They are not subsets of each other and no row-for-row mapping exists.
What is the portfolio ceiling?
One source says$2.00B–$4.50B/yr (the binder)
The other says$2.25B–$6.39B/yr (the rows, added up)
Printed both ways on purpose. Smoothing this is the thing that would cost the package its credibility. Every ceiling is BB2G’s own arithmetic and none of it is third-party validated.
How many families?
One source says7 (order-of-battle metadata)
The other says10 (counted off the rows themselves)
The metadata was written before the rows were finished. The rows are the source of truth; the metadata has not been restated.
How much of it is built?
One source says61 rows carry a monetization score and a revenue model
The other says10 deployed · 1 partial · 1 adjacent · 60 specification only
This is the reconciliation that matters. The market view scores every row as if it existed. The engine view measured which ones do. Lead with this number, not the ceiling.
The number to lead with
Ten of seventy-two.
A portfolio document says what the intellectual property might be worth. It says nothing about the rate at which it is built, and nothing about how much of it exists today. 10 of 72 rows are deployed. 60 are specification only. That figure was arrived at by correcting an earlier, more flattering count downward — and it is the reason the rest of the arithmetic deserves a hearing.
Say it before anyone finds it: nothing in this fleet can
currently take a payment. Every revenue model on these pages describes an intended commercial
structure, not a live one, and no figure on this site is a price or an offer.