TBPN: ""If we look at the next decade, if there are 200 products that are going to be manufactured in orbit, 195 of those are going to be...

"If we look at the next decade, if there are 200 products that are going to be manufactured in orbit, 195 of those are going to be pharmaceuticals." @zebulgar predicts what LEO manufacturing will look like in the coming decades: "If I had to peer into the crystal ball and look at what comes next, it's probably fiber before semis is my rough guess.". "If we look at the next decade, if there are 200 products that are going to be manufactured in orbit, 195 of those are going to be pharmaceuticals." @zebulgar predicts what LEO manufacturing will look like in the coming decades: "If I had to peer into the crystal ball and look. The BotsFired read on TBPN: this matters only where it changes a real workflow, budget, deployment constraint, or buyer decision. The signal matters only if it changes how a team builds, buys, deploys, or competes. The hard question is whether this creates measurable speed, cost, distribution, or capability advantage. For builders, the practical question is whether TBPN removes a constraint that teams already feel. A launch is cheap; a default workflow is expensive to earn. A serious buyer will ask what changes on Monday morning: which workflow gets faster, which budget moves, and which existing vendor suddenly looks exposed. For operators, the test is narrower: what work moves from manual judgment to repeatable system behavior, who approves the change, and what failure mode appears when the tool leaves the demo path?