Much of the current framing treats the orbital economy as a cost-crossover race against Earth analogs; if instead we treat coordination capacity (the ability to manage dense, robotic, multi-tenant operations in a hazardous, rights-governed environment) as the scarcest resource, how does that overturn assumptions about which industries scale first, where Wright’s-law bites hardest, and whether the main early bottleneck is physics and cost or institutional and software complexity?

Answer

Treating coordination capacity as the main scarce input flips early priorities from physics and launch cost to software, governance, and ops. Industries that are simple to coordinate but heavy or low-margin can scale earlier than ones that are light and high-margin but coordination-intensive.

1. Which industries scale first under coordination scarcity

• Earlier than usual framing:

  • Single-tenant or low-tenant platforms with narrow tasks (e.g., one-operator constellations, single-factory stations, captive servicing for one fleet).
  • Orbital testbeds with low robot density and simple ops (environmental test, niche compute for that platform’s own needs).
  • Vertically integrated stacks where one firm controls launch, platform, and primary workload, minimizing cross-firm coordination.

• Later than usual framing:

  • High-density multi-tenant industrial parks.
  • General-purpose third-party servicing across many form factors.
  • Shared debris services, shared depots, and cross-operator “utilities” that need complex rights, standards, and scheduling.
  • Open orbital cloud or manufacturing platforms that must arbitrate many customers and SLAs.

2. Where Wright’s law bites hardest

• Strongest learning effects shift to:

  • Common ops software, autonomy stacks, traffic management, and scheduling systems reused across missions.
  • Standardized coordination primitives (booking slots, robot task APIs, safety envelopes) rather than just hardware.
  • Organizational patterns (multi-mission ops centers, incident response, certification playbooks).

• Weaker or slower learning:

  • Hardware that is tightly coupled to bespoke ops and rights regimes (custom safety cases, one-off interfaces).
  • Highly multi-tenant platforms before stable governance and APIs emerge.

3. What becomes the main early bottleneck

• Bottleneck tilts toward institutional/software complexity, not pure physics, for many candidate sectors:
  • Physics and launch cost dominate for bulk power, mass cargo, and very simple constellations.
  • But for orbital manufacturing, shared compute, and cross-operator servicing, the hardest part is:
    • Proving safety and liability models for autonomous robots around other people’s assets.
    • Encoding property, access, and scheduling rights into software that many actors trust.
    • Managing human oversight and jurisdiction across time zones and regulators.

4. Implications for architecture choices

• Favor early:

  • Architectures that minimize cross-firm coupling: one operator per platform; robots mainly serving their owner.
  • Simple, coarse-grained interfaces (whole-rack leases, whole-orbit windows) rather than fine-grained task markets.
  • “Ops-first” designs: easy-mode rendezvous, large safety buffers, conservative densities.

• Delay or stage:

  • Dense multi-tenant hubs until coordination software and norms are mature.
  • Fine-grained robot labor markets (per-task, per-minute) until safety and liability tools are proven.

5. Boundary: extension of Earth vs new production environment

• With coordination scarce:
  • Orbit-as-extension grows first: captive factories and compute aligned with a single Earth firm’s processes.
  • Truly “orbit-native” environments—where many actors share dense robotic capacity—arrive later, once institutions and code for rights, safety, and scheduling are robust.
• The shift to orbit-as-new-environment is gated less by launch price and more by:
  • Reliability and composability of coordination software.
  • Governance regimes that make multi-tenant operations safe and insurable.

6. Where to expect the steepest early learning

• In:
  • Shared autonomy and ops stacks used first within firms, then carefully exposed to partners.
  • Reusable governance templates: standard service contracts, insurance patterns, and incident-protocols for robotic interaction.
• Not yet in:
  • Wide-open multi-tenant marketplaces; those wait until above layers are commoditized.

Overall: with coordination capacity scarce, the early orbital economy is dominated by relatively simple, vertically integrated, low-tenant systems. Wright’s-law runs first on shared software and governance, then on dense multi-tenant hardware once those layers stabilize. For many promising industries the decisive constraint is institutional and software complexity rather than launch price or raw physics, at least in the first wave after launch-cost collapse.