# Simplycity — 10-minute demo script

**Audience:** investor, hospital partner, operator or city officer · **Setup:** open `/platform/` (or the public IP on port 8080). Everything shown is a sandbox with simulated aircraft.

## Before you start (1 min)

Say what it is and what it is not: "Simplycity is the coordination and evidence layer. We don't build or fly aircraft. This is a working platform driving a *simulated* SC-17 so you can see the whole loop."

## 1. The loop in one run (3 min) — "The 17-minute corridor"

Click **Watch a guided demo**, then **Run this demo** on *The 17-minute corridor*. Talk over the steps as they tick off on the right and the aircraft crosses the map:

1. A hospital clinician requests a blood-sample transfer (opaque order reference; no patient data).
2. The origin hub scans the sealed cassette: mass, temperature, seal, custody opened.
3. The operator runs **12 release gates on live data**. Open the mission to show the checklist.
4. A **named operator** signs the release. The snapshot stores every input and the rule version.
5. The aircraft flies the approved corridor; energy, altitude and route adherence are recorded.
6. The receiving hub accepts the cassette; the mission reconciles and closes.

Land the point: "Every step had an owner, and every decision is in an append-only ledger."

## 2. The system says no (3 min) — "Saying NO — and fixing it"

Run the second script. The first aircraft has too little energy for route plus reserve. Flow **refuses the release with a named reason and a fix owner**; the operator swaps aircraft and the mission proceeds. Then open **Trust ledger** and show `RELEASE_DENIED` — "the refusal is evidence too."

## 3. When things go wrong (3 min) — "Weather closes the corridor"

Run the third script. A storm arrives mid-flight: a critical alert, the operator holds and orders a return, the cassette is recovered, and an **incident review** closes with a recorded root cause. Then run *Lose the link, keep the record* if time allows: telemetry drops, the last known position is kept, the outage is reconciled afterwards.

## 4. Proof and trust (2 min)

- **Trust ledger** → *Verify entire chain*, then *Prove tamper-evidence* (edits a copy and shows detection).
- **Impact** → scorecard against the pilot's decision test, on-time rate, energy per km, interventions per 100 missions. Point at the SANDBOX banner: the history is synthetic and flagged; switch to *Live sandbox only* to see what you just ran.
- **Community page** (`/community/`) → "what the public sees, what we will and won't publish."

## 5. Business and integration (optional)

- **Unit economics** (`/platform/economics.html`): change corridors, fees and costs; note the model excludes aircraft, fleet margin and any unvalidated volume curve.
- **Integration contract** (`/platform/api.html`): "this is what an OEM or operator provides; the simulator uses the same endpoint."

## Hard questions to expect

| Question | Honest answer |
|---|---|
| Is this connected to a real aircraft? | No. It is connected to a simulator through the same telemetry contract a real OEM would use. |
| Are the numbers real? | Simulated flights follow the SC-17 planning model; history is synthetic and flagged. The pilot exists to produce real numbers. |
| Who is liable for a flight decision? | The licensed operator retains flight responsibility. Simplycity records the decision and enforces the operator's approved rules. |
| What stops someone editing the log? | Hash chain plus database refusal of edits; verification finds offline tampering. |
| What is missing before a pilot? | A real operator and OEM integration, approved weather/airspace sources, TLS and SSO, a security review, and agreed data terms. |

## Privileged roles

Operator manager and Administrator need the sandbox passcode (kept by the platform owner in `data/admin_passcode.txt`). The administrator can change weather, degrade links and reset the sandbox; those actions are themselves ledgered.