Everything here is ordered, and the ordering is not the inventor's opinion of her own work. Each item carries five scores — revenue ceiling, build readiness, IP protection, partner fit, mission impact — and the weights are on screen. Whichever order the room chooses, that is the order that gets handed over.
Two figures, two calculations, both shown. The binder states a portfolio-wide illustrative ceiling; the page adds up the individual rows. Neither is a forecast. Every figure on this site is read out of apps.json when the page loads — none of them is typed into the copy, so a stale number cannot survive here.
Four surfaces
All items, one order
Five weight sliders, five presets, filters by family, tier, priority and IP status. Exports the ranked CSV and the Build Now pack in the room, with no connection.
Four agents on the same data
The Analyst, the Skeptic, Counsel and the Briefer. Each one is grounded on the list itself and each one is told where its line is — Counsel will not go past fit into mechanism.
Talking notes
The opening in four sentences, the frame to hold all morning, the four hard questions with answers already written, and the close.
What is actually built
The list is the IP and revenue view. It does not say what is deployed. This is the map from each row to the repos and hosts that implement it — and the deployments that map to no row at all.
The IP position, stated first
Copyright protects the written work and the source code. It does not protect the mechanisms. Those need the provisional filing, and the twelve-month public-disclosure clock is already running — which is why sequencing is a constraint here and not a preference.
The deck (PDF) · The deck (PPTX) · The revenue model (XLSX) · apps.json · apps.csv