LIFE CYCLE OF AN ORDER
(Tranquility 1 / Tranquility 2 framing)
- 1) Executive Summary
This white paper defines an end-to-end “order lifecycle” for Tranquility: how an order is received on Earth,
translated into a physical and/or digital delivery plan, executed via launch and lunar operations, and ultimately
delivered back to a customer in the form they actually consume—compute time, models, results, artifacts, and
(sometimes) returned hardware.
Two truths shape the design:
The Moon facility is a modular industrial system: reactor modules, compute modules, radiators, robots,
spares—shipped in volume and swapped, not “repaired in place” at component level. The core plan assumes
containerized thorium reactor modules (~40 MWe each) and modular compute that gets swapped as units.
tranquility-paper tranquility-paper tranquility-paper
Launch cadence is the supply chain: the ramp to gigawatt-scale compute depends on consistent Starship-class
delivery at industrial tempo (e.g., 30–38 launches in 2029; 30–40 in 2030; then final pushes to target).
tranquility-paper tranquility-paper
Tranquility 1 is the initial site to ~3.5 GW class operations (target achieved ~2031, mature utilization ~2032).
Tranquility 2 is the second-site concept (Earth-facing ops and scale path), aligned with Phase 2 expansion
planning (10 GW and beyond).
tranquility-paper
- 2) What Is “An Order”?
Tranquility supports two intertwined order types:
A) Compute Order (Customer-facing)
A customer purchases reserved capacity contracts and runs training workloads at market-like pricing (example:
~$3/GPU-hour cited as market rate with reserved capacity contracts).
tranquility-paper
pinkhouse.tech Page 1 of 11 January 2026
Deliverables to the customer (“customer loading docks”) are typically:
trained model weights / checkpoints
evaluation reports
safety / compliance attestations
dataset transforms, embeddings, derived artifacts
invoices, audit logs, SLA reports
B) Logistics Order (Operations-facing)
Tranquility operations place internal orders for:
compute modules (new or replacement)
reactor modules
radiator panels
robots / spare parts / comms gear
These physical orders are what keep the compute orders possible.
In practice, a compute order generates a demand signal that triggers logistics orders (capacity expansion,
refresh cycles, spares).
- 3) Actors and “Docks”
Earth-side actors
Customer (AI lab, enterprise, academic, consortium member)
Tranquility Order Desk (contracts, capacity scheduling, compliance)
Earth Delivery Docks (EDD) (receiving + staging hub)
Integration & Test Yard (payload acceptance test; “ready-to-fly”
certification)
pinkhouse.tech Page 2 of 11 January 2026
Launch Provider / Starship Operations (mission integration, launch,
landing)
Lunar-side actors
Lunar Receiving & Offload Zone (LROZ) (landing-adjacent staging)
Autonomous Transport & Handling (robot fleet; dust-tolerant ops)
Tranquility Site Ops (power, thermal, compute, maintenance)
Governance / Security (access control, audit, incident response)
Return Logistics Cell (pack-out, load-back, manifest, return)
Customer “loading docks”
Customer’s secure storage endpoints (cloud bucket / vault)
Customer’s training pipelines (CI/CD for models)
Customer’s compliance and procurement systems (billing + audit)
- 4) End-to-End Lifecycle (One Diagram)
A single order becomes two synchronized flows:
Digital flow (Compute Service)
Physical flow (Capacity & Maintenance Supply Chain)
Lifecycle at a glance
Order Intake → Plan → Build/Stage → Fly → Receive → Integrate → Run → Deliver →
Refresh/Return → Close
pinkhouse.tech Page 3 of 11 January 2026
- 5) Phase-by-Phase Lifecycle (Detailed)
Phase 0 — Preconditions: Capacity exists (or is being built)
The baseline architecture assumes containerized reactor modules and modular compute delivered by heavy-lift
lunar missions. Example budgeting/scale logic: ~80 Starship flights at ~100 tons each to deploy ~8,000 tons
total mass (reactors, compute modules, radiators, robots/comms/spares).
tranquility-paper
Power target example: ~3.5 GW requiring ~88–90 reactor modules at ~40 MWe each (rounded up for
redundancy).
tranquility-paper
tranquility-paper
Phase 1 — Order Intake (Customer → Tranquility)
Inputs
customer identity + legal entity
workload type (training / fine-tune / eval / batch inference overflow)
security posture (data sensitivity, export controls, “no-human-access” constraints)
requested capacity profile (GPU-equivalents, duration, deadline)
delivery expectations (what “done” looks like)
Outputs
reserved capacity contract
execution window reservation
compliance/audit plan
acceptance criteria (“customer loading docks” definition)
Notes
The system anticipates reserved capacity contracts at market pricing. tranquility-paper
pinkhouse.tech Page 4 of 11 January 2026
Phase 2 — Capacity Scheduling & Work Package Creation
Tranquility converts the order into a Work Package:
capacity block reservation (start/stop times, priority)
dataset ingress plan (secure transfer, checksums, encryption keys)
compute topology plan (model parallelism, cluster allocation)
“deliverable manifest” (weights, reports, logs)
billing meter definition
If insufficient capacity exists, this phase emits an Ops Demand Signal that may trigger
Phase 3 (logistics procurement).
Phase 3 — Logistics Procurement (Internal “Order”)
When Tranquility must build or refresh capacity, it places a logistics order:
Example mass logic
reactor modules, compute modules, radiator panels, robots/spares/comms, all accounted into a tonnage plan
that maps to Starship flights. tranquility-paper
Example business logic
launch services priced per successful landing (payment-on-delivery aligns incentives). tranquility-paper
Outputs
Bill of Materials (BOM)
flight manifest allocation
QA + test protocols
shipping schedule to Earth Delivery Docks
Phase 4 — Earth Delivery Docks (EDD): Receive → Stage → Certify
This is the “industrial throat” where chaos is converted into reliability.
pinkhouse.tech Page 5 of 11 January 2026
EDD functions
receive modules from manufacturers
verify serials, weights, seals, tamper evidence
perform acceptance tests (power-up, comms handshake, vibration packaging integrity)
containerize to flight-standard interfaces
manifest to a specific lunar mission
Key design choice
Ship as modules, not as artisanal assemblies. The lunar side is designed around swap-and-replace, matching
the “modular replacement” concept. tranquility-paper
Phase 5 — Launch Integration → Flight → Lunar Landing
Integration
payload integration to Starship lunar mission profiles
refueling choreography handled as part of mission assumptions (not detailed here)
Landing
deliver to lunar surface with standardized offload plan
Risk reality
If launch failures trigger regulatory grounding, the supply chain can stall for months; plan for buffer inventory
and schedule resilience. tranquility-paper
Phase 6 — Lunar Receiving & Offload (LROZ): “Receipt at Moon Docks”
On touchdown, the Moon has its own version of “delivery docks”:
Receipt steps
landing verification + site safety confirmation
pinkhouse.tech Page 6 of 11 January 2026
offload to staging pads
robotic move to quarantine/inspection
acceptance tests (power, comms, thermal interfaces)
Operational reality
dust is a persistent adversary; robot failures are expected and drive iterative procedure refinement.
tranquility-paper
Phase 7 — Site Integration: Install → Commission → Add to Capacity Pool
For reactor modules
placement + thermal coupling
control system integration
staged commissioning to power bus
A modular reactor strategy is explicitly assumed (container-sized thorium MSR modules).
tranquility-paper
For compute modules
placement + radiation/thermal interface verification
attach to power and network fabrics
burn-in tests, then admission into the scheduler pool
For radiator panels
deploy + verify heat pipe continuity and radiative performance
Phase 8 — Run the Customer Workload (The “Compute Order” is fulfilled)
Now the “order” becomes time on the system:
Run steps
pinkhouse.tech Page 7 of 11 January 2026
dataset ingress + validation
training execution (with checkpointing)
evaluation suite
packaging outputs for delivery
produce audit and billing artifacts
Service posture
reserved capacity contracts underpin predictability for customers. tranquility-paper
Phase 9 — Delivery to Customer Loading Docks
“Delivery” is not a rocket landing; it’s a manifest of artifacts deposited into customer-controlled endpoints.
Deliverables
model weights/checkpoints
eval + red-team reports (if requested)
cryptographic provenance hashes (what ran, where, when)
usage statement for billing
SLA report
This phase closes the compute order.
Phase 10 — Refresh / Replace / Return (The Long Tail)
Even after delivery, the system must remain industrially healthy.
Replacement cycle
compute modules reach end-of-life and are swapped as units (example milestone: “first compute module
replacement” appears as an operational milestone in 2029). tranquility-paper
Robotics scaling
pinkhouse.tech Page 8 of 11 January 2026
robot fleet expands with ongoing maintenance needs (example: expands to 20 units). tranquility-paper
Crew rotations (optional)
human rotations may begin once the economics justify it; example: “first crew rotation arrives (probably 2032)”
with 4–6 engineers on 90-day missions, then potentially becomes permanent. tranquility-paper
Return logistics Some modules/components may be returned to Earth for:
refurbishment
forensic failure analysis
recycling/high-value recovery
vendor warranty loops
Return is packaged as:
“Return Order” manifest
load-back plan
Earth receiving + audit trail
close-out report (feeds reliability engineering)
- 6) Timeline View (Anchored to Tranquility ramp)
A practical lifecycle exists inside a broader ramp schedule:
2029: aggressive deployment (30–38 launches), capacity reaching ~2–2.5 GW; first compute module
replacements begin; robot fleet expands. tranquility-paper
2030: path to ~3–3.5 GW with similar launch cadence (30–40).
tranquility-paper
2031: final 10–20 launches to hit full ~3.5 GW target. tranquility-paper
2032: mature operations, higher utilization; crew rotation likely begins.
tranquility-paper
pinkhouse.tech Page 9 of 11 January 2026
Phase 2 planning: expand to 10 GW; lunar thorium mining feasibility; second site
selection (Earth-facing operations). tranquility-paper
(Your Tranquility 2 “60 GW net” vision can be treated as Phase 2/3 extension; the paper’s internal anchors
above are what the current master doc explicitly states.)
- 7) Minimum-Viability Operating Model (Low Involvement)
If you want this to be “low-touch” for you, the order lifecycle should be paired with two automations:
Standardized templates
Work Package template (for compute orders)
Logistics BOM template (for physical orders)
Acceptance Test checklist (Earth and Moon)
Delivery Manifest template (customer outputs)
Exception-driven management
you don’t “manage orders,” you only handle exceptions:
launch delay beyond X days
acceptance test failure
SLA risk (capacity shortfall)
security/compliance anomaly
Everything else is boring machinery.
- 8) Appendix A — A “Feelgood” Micro-Fiction (One Order)
On Earth, the customer’s procurement bot submits a reserved capacity renewal at 02:14 UTC. No drama. The
Order Desk replies in seconds: window confirmed, audit profile unchanged, delivery endpoint the same vault as
last quarter.
At the Earth Delivery Docks, nobody talks about destiny. They talk about seals, manifests, and whether a
connector’s dust cap is the right polymer. A compute module rolls through acceptance like a suitcase through
an airport—x-rayed, verified, stamped, staged. It’s not romantic. That’s the point.
pinkhouse.tech Page 10 of 11 January 2026
Three days after launch (assumed typical transfer; not the hard part) the Moon receives it the way the Moon
receives everything: silent, cold, absolute. Robots approach like careful insects. The staging pad lights flicker; a
comms handshake passes. The system logs a simple line: RECEIVED — INTACT.
Later, far from the dust and the radiators, the customer’s model trains. Not as a miracle—just as work. The
weights land in the customer vault with checksums and provenance, and the Order Desk’s closing note is a
single sentence:
“Delivery complete. Next window held. Have a good build.”
That’s what the future feels like when it’s functioning: not loud. Just reliable.
pinkhouse.tech Page 11 of 11 January 2026