If we combine a rights-centric framing (orbital slots, debris budgets, servicing corridors as tradable assets) with a demand-constrained orbital economy, how do different orbital-rights designs (simple per-object caps, tradable debris allowances, time-limited lane licenses) change which physical industries—orbital compute, microgravity manufacturing, servicing, or pop-up swarms—reach cost crossover first, and can we identify a small set of rights primitives that both control externalities and avoid choking off early industrial learning curves?

Answer

Per-object caps favor low-count, high-value assets (orbital compute, bespoke manufacturing) and penalize pop-up swarms; tradable debris allowances favor pop-up swarms and servicing; time-limited lane licenses favor servicing and microgravity manufacturing that use predictable, longer-lived orbits. A small set of primitives—(1) per-orbit capacity caps, (2) tradable debris/“risk” budgets, and (3) time-bounded lane or volume licenses with embedded servicing rights—can manage externalities while preserving learning for all four.

Relative effects on industries under each design (demand-constrained, cheap launch)

• Simple per-object caps

  • Orbital compute: helped – few, dense platforms fit under caps.
  • Microgravity manufacturing: neutral/positive – small number of factories per orbit.
  • Servicing: hurt – fewer clients and less debris; weaker volume for learning.
  • Pop-up swarms: strongly hurt – object count is binding; swarms lose cost edge.

• Tradable debris allowances (per expected-risk unit, not per object)

  • Orbital compute: neutral – long-lived, low-maneuver platforms buy small allowances.
  • Microgravity manufacturing: mixed – clean factories OK; messy lines pay more.
  • Servicing: helped – can earn allowances by cleanup; becomes rights arbitrage + physical.
  • Pop-up swarms: helped if cleanly deorbited – they buy short-lived allowances and arbitrage high value/time.

• Time-limited lane / volume licenses (capacity per lane; slots re-auctioned)

  • Orbital compute: mixed – good if long terms; bad if short, since migration is costly.
  • Microgravity manufacturing: helped – predictable tenure allows amortizing factories; lane reuse supports learning.
  • Servicing: helped – licenses can bundle servicing corridors; dense, recurring traffic.
  • Pop-up swarms: mixed – OK if short-term lane slices exist; bad if lanes optimized for long stays.

Rights primitives that balance control vs learning

• P1: Orbit/volume capacity caps (per shell/lane) on aggregate collision risk, not object count.
• P2: Tradable debris / risk budgets per operator, with credits for verified cleanup and safe deorbit.
• P3: Time-bounded occupancy licenses for specific lanes/volumes, with:
  • minimum safety rules,
  • optional sub-leasing to pop-ups,
  • attached rights/obligations for inspection and servicing access.

With P1–P3:

• Orbital compute and microgravity manufacturing get predictable, multi-year lanes (P3) under aggregate risk caps (P1), so they can build few, larger platforms and ride Wright’s-law on internal reuse.
• Pop-up swarms operate as tenants inside lane holders’ rights or buy short-lived risk budgets (P2), so they are constrained by externalities but not banned.
• Servicing gains both a physical market (more assets to serve) and a rights market (earning or brokering P2, operating under P3 corridors), which steepens its learning curve.

This mix likely makes servicing and pop-up architectures reach cost crossover first (supported by P2), with orbital compute and then microgravity manufacturing following as P3 lanes stabilize and demand thickens.