“Cargo tools today rank loads by price and assume a live link. We built a planner that measures a manifest in days a base goes without, so a bid can never outrank someone's air. Its rules are deterministic, so Earth and Mars can each compute the manifest and confirm it with one 8-character code across a 44-minute delay. And its request desk turns one message from a crew into a booking and asks every missing question at once.”

About 25 seconds out loud. The originality table on the idea page backs up each claim.

Tick steps off while you rehearse. Ticks are kept in this browser only.

1. 1.From the landing page, click Open the console.Point at the green line at the top and the Mars card: miss MS-07 and the next rocket leaves 26 months later.20 s
2. 2.Open What's on the rocket.MS-07 is nearly full and everything fits. The line at the bottom says Earth and the base hold the same plan.15 s
3. 3.Back in the inbox, open Cmdr. Okafor's message and click Turn into a booking.Claude fills it in as life-critical, with a need date worked out from the 294 days of oxygen reserve.30 s
4. 4.Click Add to the plan.What changed says one other load now arrives late: the rover fleet moves to MS-08, 19 months late.20 s
5. 5.Open Kepler Mining and click Turn into a booking.Weight and space are missing, so Add to the plan stays off. Both questions go back in one message.20 s
6. 6.Under Try what happens if…, apply Greenhouse expansion approved.Every paid load moves to a later rocket, but no base goes short: money gave way, survival didn't.10 s
7. 7.Apply Crew grows from 6 to 8.The line at the top turns red: the greenhouse LED panels arrive 21 months late and Ares Outpost goes 650 days short.10 s
8. 8.Click Write the update.Claude drafts the note to the commander and one line for each company whose cargo moved.20 s
9. 9.Click the Shackleton Base card.On the Moon, moved loads wait four weeks for the next rocket and still arrive on time. That contrast is the point.10 s

1. 1.Open the deployed app on the presenting laptop.Zoom until the inbox and the side panels sit side by side.
2. 2.Check the status pill at the top says "Claude online".If it says "No AI key", set ANTHROPIC_API_KEY on the server and restart it.
3. 3.Run the whole click path once shortly before going on.It warms the server up and shows Claude's response time on the venue network.
4. 4.Press Start over right before you start.
5. 5.Decide who talks and who clicks.

• Claude is busy or the key is missing: the offline reader and the brief template take over by themselves. Say it out loud: “This is the mode a base uses during a blackout.”
• A wrong click: press Start over and jump back in at Try what happens if….
• The server is unreachable: the browser carries its own copy of the planner, so everything except Claude keeps working. The status pill switches to “Offline”.

• AI in the product: Claude reads requests and drafts briefs, called from our FastAPI server with the Anthropic Python SDK. It never decides what flies.
• AI used to build it: Claude Code, Anthropic's coding assistant (model Claude Opus 5.5), wrote most of the code, documentation and screenshots under the team's direction. Every member should be able to explain the packer, the need-date check, the fingerprint and the limits on the AI.
• External resources: FastAPI, Pydantic, Uvicorn and the Anthropic Python SDK on the server; Next.js, Tailwind CSS, shadcn/ui and PptxGenJS in the web app; Google Fonts and the public FNV-1a hash algorithm.