Cargo Window

Admin view. The team's notes for presenting Cargo Window. Users of the console never need these pages.

Beyond 2030 · Our idea

Miss the ship to Mars and you wait 26 months.

Cargo Window plans what flies to the first bases on the Moon and Mars. It measures every manifest in the days a base goes without, never lets a bid outrank survival, and works across a 44-minute signal delay.

26months

Between low-energy launch windows from Earth to Mars. Miss one and the next ship is two years away.

~7months

Trip time to Mars on a typical transfer. What is on board was decided long before it is needed.

3–22min

One-way signal delay between Earth and Mars. A question and its answer can take 44 minutes.

~2weeks

Contact with Mars drops every 26 months, when the Sun sits between the planets.

1 · The problem

Deciding what flies when the next ship is two years away

Every rocket to an off-world base has a fixed mass and volume, and in 2035 every flight has more cargo waiting than room. Someone has to choose what goes. On Earth that choice is cheap to get wrong, because the next truck leaves tomorrow. To Mars, the next ship leaves in about 26 months, so the manifest decides who goes without for two years.

Today manifests for a handful of government missions are built by hand, in spreadsheets and meetings. That stops working once several bases and dozens of companies share each flight. Three things break at once:

  • Fairness: there are no shared, published rules for who gets bumped, so money or politics decides.
  • Foresight: nobody sees that a bumped load leaves a base short until the ship lands without it.
  • Requests: crews ask over a delayed link, and every clarifying question to Mars costs up to 44 minutes.

2 · Who it affects

Five groups, one rocket

WhoWhat goes wrong for them today
Base crewsA spare part they needed lands on the next ship, months after the old one fails.
Base commandersThey learn about a shortage when the ship arrives without it, with no time left to plan around it.
Cargo officers on EarthRequests arrive as messy messages over a delayed link, and every follow-up question costs a round trip.
Flight operatorsThey must fill every kilogram and justify every refusal to agencies and paying customers.
Companies shipping cargoThey pay for space and find out late that their load was bumped, with no reason given.

3 · Why it matters

A bumped load can be a health risk for two years

  • The stakes are lives, not delays. A CO₂ scrubber cartridge that misses the Mars window leaves a crew short of air-cleaning spares until the next one.
  • Every kilogram is expensive. Delivering cargo to the Moon costs hundreds of thousands of dollars per kilogram today. Wasted room is wasted money.
  • Sharing needs trust. Agencies and companies will only share flights if the rules are fair, published and the same for everyone.
  • Bases can't fix it alone. By the time a crew notices a part is missing, the window has closed.

4 · How it emerges

From today's lunar deliveries to full Mars windows

  1. 2018

    FACTNASA starts buying cargo deliveries to the Moon from private companies.

  2. 2020s

    FACTArtemis aims for a lasting human presence near the lunar south pole. Reusable heavy rockets push the cost per kilogram down.

  3. Early 2030s

    ASSUMPTIONA permanent lunar base with flights every few weeks. Mining, research, media and tourism companies buy space next to agencies.

  4. 2035

    ASSUMPTIONA first small crewed outpost on Mars, fully dependent on cargo from Earth and reachable only in windows about 26 months apart.

  5. Then

    ASSUMPTIONEvery flight is oversubscribed, and the manifest becomes the most contested decision in the program.

Why today's tools won't cope

  • Freight software optimises cost or revenue. A missed slot on Earth costs a day.
  • Airline cargo bumps by fare. Off Earth, the highest payer must never outrank a CO₂ scrubber.
  • Planning tools assume a live link to one central system. Mars is 22 minutes away and sometimes unreachable.

Why our answer holds up

  • The 26-month window and the signal delay are physics, not guesses.
  • The first step, commercial lunar cargo, already exists.
  • The problem grows with every base and every company that joins.

Precedent

It already happens on Earth, on a small scale

The problem isn't invented. Places that are hard to reach already live by resupply windows, and they plan them by hand.

  • Antarctica: the South Pole station gets no flights for about eight months of winter. What misses the last summer flight waits until spring.
  • The space station: cargo flights are packed against priority lists, and when a flight is cut back, lower-priority items stay on the ground.
  • Remote islands and research ships: supplies come with scheduled ships, and a missed sailing means weeks or months without.

Off-world bases take the same problem and make it bigger, slower to fix and less forgiving. The planning tools haven't caught up.

5 · What the solution does

Ask, decide, show the cost, agree

Request desk

AI

Crews write what they need in their own words. Claude turns the message into a booking draft, works out the need date from what's left in stock, and puts every missing detail into one reply.

Packer

RULES

Published, fixed rules decide what flies: life-critical first, then mission-critical, then commercial by bid. Money only sorts the commercial tier.

Consequence board

RULES

Every load is checked against the date its base needs it. Each manifest is measured in days a base goes short, with late loads in red, months before launch.

Manifest fingerprint

RULES

An 8-character code computed from each manifest. Earth and the base compare codes in one short message to confirm they hold the same plan.

Briefs

AI

Claude drafts the note to the commander and the message to each bumped shipper, using only the planner's numbers. A person checks it and sends it.

6 · Technologies

Each one earns its place

TechnologyWhat it does hereWhy it belongs
Rule-based packer, our own code in Python and TypeScriptBuilds every manifest: Python on the Earth server, TypeScript in the browser as the base copyDecisions about air and food must be predictable and explainable. Same inputs give the same manifest on both planets, and a test proves the two copies agree.
Python, FastAPI and PydanticThe Earth server: packing, the request desk and briefs behind a typed APITyped models reject bad input at the door, and FastAPI documents the API for free.
Claude, through the Anthropic Python SDKReads free-text requests into booking drafts and drafts briefs, on the serverRequests are messy and urgent, and each follow-up question costs a 44-minute round trip. One good reading saves hours. The API key stays on the server.
Next.js, Tailwind CSS and shadcn/uiThe console and these admin pagesAccessible, consistent components for a tool people use under pressure. Builds to static files the Python server hosts.
Manifest fingerprint (FNV-1a hash)Turns a manifest into an 8-character codeTwo planets confirm they agree with one tiny message instead of resending the whole manifest.
Docker and RenderShips the server and the console as one serviceOne container, one URL, deployed from the repository.

Left out on purpose

  • Blockchain: one operator with signed bookings is enough. A chain adds cost and slow agreement between planets.
  • An optimisation solver or machine learning for packing: a commander can't check its answers. Fixed rules can be checked step by step.
  • A database: the server is stateless and the browser holds the scenario. Production adds a shared store and signed bookings.

7 · Design and build

AI reads and writes. Rules decide. People approve.

Never guess a number

A missing mass or date stays missing and blocks the booking. The server checks every field Claude returns.

Same inputs, same manifest

No randomness and no AI in the decision, so Earth and the base can each compute it and agree.

Measure what people feel

A manifest is scored by days a base goes short, not by kilograms carried or revenue earned.

A person signs off

Claude drafts bookings and messages. Nothing is booked or sent without a cargo officer.

  1. 01PEOPLECrew writes a requestIn plain words, under pressure, over a delayed link.
  2. 02AIClaude drafts the bookingLoad, class, mass, volume, need date. Missing facts become questions.
  3. 03PEOPLECargo officer approvesMissing numbers block it. Nothing is guessed.
  4. 04RULESPacker builds manifestsFlight by flight, in a fixed order, one reason per decision.
  5. 05RULESBoard shows the costArrival against need date, days a base goes short, fingerprint.
  6. 06AIClaude drafts the briefsThe officer edits and sends them to the base and each shipper.
for each base:
  waiting = every booking for that base
  for each flight to that base, in launch order:
    sort waiting by class: life-critical, mission-critical, commercial
      inside life and mission: earliest need date first
      inside commercial: highest bid per kg first
    for each load in that order:
      if it fits the mass and volume left: put it on this flight
      otherwise: it waits for the next flight
for each load:
  arrives    = launch + trip days
  days short = arrives - need date   (late if above zero)

Originality

What we created that wasn't already there

A cargo planner that measures a manifest in the days people go without, where money can never outrank survival, that two planets can run separately and still agree on, and that gathers every missing fact in one message across a 44-minute delay.

What exists todayWhat we added
Freight and airline cargo tools rank loads by cost or fare.A class order where money only sorts the commercial tier. Survival can never be outbid.
Planners report kilograms used and revenue earned.Days a base goes short as the measure of a manifest, checked for every load against the date its base runs out.
Planning tools assume a live link to one central system.A deterministic packer plus a fingerprint, so Earth and a base compute the same manifest on their own and confirm it in one short message.
Forms and chat assume instant back-and-forth.A request desk built for delay: one message becomes a booking draft, every missing question goes back in one reply, and it still works offline.

Built by us

  • The packer in Python and TypeScript, the need-date check and the days-short measure.
  • The manifest fingerprint, and a test that runs both packers on the same bookings and compares them.
  • The FastAPI server: request desk and briefs, with checks on every field Claude returns.
  • The console and these pages.

Borrowed and credited

  • Claude, through the Anthropic Python SDK, for reading requests and drafting briefs.
  • FastAPI, Pydantic, Uvicorn, Next.js, Tailwind CSS and shadcn/ui.
  • Google Fonts: Schibsted Grotesk and IBM Plex Mono.
  • PptxGenJS, for the PowerPoint download of the pitch deck.
  • The FNV-1a hash, a public algorithm.

The 2030+ test

Three questions every project must pass

Why will this problem exist?

Cheaper reusable launches and permanent bases create more cargo than room, and orbital mechanics limits Mars flights to windows about 26 months apart.

Why does it matter?

A wrong manifest can leave a crew without air-cleaning spares, water parts or medicine for up to two years, and nobody finds out until the ship lands.

Why is our solution the right one?

It makes the choice fair and predictable, shows the human cost before launch, and keeps working across delay and blackout.

Business and impact

Who pays and what changes

Who pays

  • Flight operators license it to plan and sell their capacity.
  • Base agencies use the request desk and the board for their crews.
  • A small fee on each commercial booking made through it.

What changes

  • Shortages show up months before launch, while there is still time to act.
  • Companies get fair, published rules and a reason for every bump.
  • Every decision is recorded and can be reviewed afterwards.

Next

After the hackathon

  • Need dates from base data: forecast when scrubbers, filters and food run out from how fast the base uses them.
  • A full copy at each base that syncs signed bookings when the link is up and compares fingerprints.
  • Return cargo (samples back to Earth), hazardous goods rules and centre of gravity.
  • Signed bookings and an audit log, so nobody can quietly change a priority.
  • A priority policy the bases and operators sign in advance, so the classes themselves are agreed before any flight is full.
  • Voice requests as recorded messages: crews in suits or mid-repair speak a request, it is transcribed at the base and sent as one message. Live voice agents don't fit a 44-minute round trip.

Example scenario. Bases, companies, people, prices and capacities are invented. Mars launch timing, trip length, signal delay and solar conjunction follow real orbital mechanics.