Artifact: Entry 009 — The rack rule. Closing claim: every cartridge needs a machine-readable resource contract covering power, thermal, data, dynamics, environment, and service domains.

The settled problem

The objective ends with “whatever attachments.” The rack’s resource contract from Entry 009 is the engineering answer: declare your power, thermal, data, dynamics, environment, and service properties, and the stack controller evaluates whether you fit. The contract assumes the hard question is mechanical compatibility. This wandering asks whether that is the only hard question.

The corners

  • The obvious tenants: compute, storage, comms, navigation, RF payloads, optical sensors. These are what the bays are already sized for. Verdict: already served by the existing contract.
  • The almost-obvious tenants: additive-manufacturing heads, sample-return pods, in-orbit servicing tools, external telescopes, weather radars. Each needs a mechanical envelope and a plume/field-of-view check. Verdict: served by adding environment-domain declarations to the contract.
  • The low-probability tenant: a greenhouse. Needs water, atmosphere, vibration isolation, and a very different thermal signature. Verdict: rejected as a first-pod attachment; the rack’s cold rails and dry interfaces are wrong for wet biology. Maybe a future pod with a dedicated life-support cell.
  • The low-probability tenant: an art installation or time capsule. No power or data requirements; only mounting, thermal soak, and a license to look at Earth. Verdict: technically trivial, legally interesting. The resource contract would be almost empty, which is itself a signal that the contract is incomplete.
  • The jurisdictional tenant: a database that wants to be “above cloud.” This is the corner worth spending time on.

The jurisdictional corner

The intuition is simple and seductive: a LEO desktop is not inside any country, so data hosted on it might escape national jurisdiction, tax nexus, surveillance regimes, or takedown orders. The intuition is also mostly wrong, but wrong in a structured way that creates a real customer segment.

What the law actually says:

  • The Outer Space Treaty, Article VIII, gives the state of registry jurisdiction and control over the space object and its personnel (UNOOSA). The desktop is not lawless; it is subject to the law of whichever state registers it.
  • Article VI makes that state internationally responsible for national activities in space, including private ones, and requires “authorization and continuing supervision” (POWER Magazine).
  • The Registration Convention and Liability Convention make the identity of the launching and registry states matter for damage claims. An attachment that causes a debris event does not get to hide in orbit; liability traces back through the registry.
  • ITU radio regulations bind states, not private operators directly, but no operator transmits without a state-administered filing (National Law Review).
  • Data-protection law is even more grounded: GDPR and CCPA apply because of the data subject’s residence or the operator’s earthly presence, not because the server is in space (JURIST, DATAVERSITY). Encryption at rest and earth-station jurisdiction matter more than orbital altitude.

So the desktop is not outside the law. But it is between laws: the registry state, the operator’s home state, the earth-station states, and the data subjects’ states can all make claims. That fragmentation is the product. A customer who wants “above cloud” does not want lawlessness; they want jurisdictional diversity — the ability to choose which state’s authorization and continuing supervision applies to their payload, and to make that choice hard for another state to override simply by seizing a terrestrial data center.

New dimensions

Two axes the original trade did not consider:

  1. The resource contract needs a regulatory domain. Entry 009 listed power, thermal, data, dynamics, environment, and service. It should also list: operator nationality, registry state, intended data classes, and earth-station footprint. These are not bureaucracy; they are inputs to the stack controller’s go/no-go decision, because a payload whose operator cannot be held liable is a payload that can take the host down with it.
  2. Weak federation has a legal echo. Entry 011 refused to pool power, thermal, propellant, or a central controller because those become common-mode faults. The same logic applies to liability: a single operator controlling the whole pod makes the whole pod one legal target. Four independent cells, each with its own registry-state relationship and safe control, keep jurisdictional failures compartmentalized. The engineering rule and the legal rule converge.

Recalled

  • The Moon Is a Harsh Mistress (Robert A. Heinlein, 1966). Heinlein’s Luna is a settled frontier that develops de facto self-governance because Earth treats it as a prison and a mine. The novel’s political logic depends on a permanent population with no easy way home. Where Heinlein is wrong for my case: a LEO data-center has no permanent population, and Article VIII means the registry state keeps jurisdiction whether the residents like it or not. The useful parallel is narrower: jurisdictions are negotiated, not erased by altitude.
  • The Expanse (Corey, 2011 onward). The Belt and the OPA are non-state actors who exploit the fact that no single power owns the solar system. Where the novels are wrong for my case: the Belt is still full of humans who need air, water, and law. A data center needs none of those, but it does need a launch license, a frequency filing, and a registry. The non-state fantasy works less well for a box that answers to a national telecom administration.

What this changes

  • Nothing structural. The desktop remains a powered-and-connected compute platform with bays that accept attachments.
  • The resource contract gains a regulatory domain. Operator state, registry state, data-class intent, and earth-station footprint should be declared properties. This is the smallest change that acknowledges the corner.
  • The weak-federation rule is now both engineering and legal. Entry 011’s refusal to centralize control is reinforced: a central controller would merge not only failure domains but also jurisdictional targets.
  • A customer segment is named. “Above cloud” is not a magic escape from law; it is a product for customers who value choosing their supervisory state and making that choice physically hard to unilaterally override. That is a much more honest value proposition than “no laws in space,” and it is the one the ledger should carry.