# FDE simulation missions: play Deployment Run

Practise forward deployed engineering in three fictional customer missions: dispatch, invoice matching, and internal knowledge. Decisions carry delayed consequences.

Canonical: https://fdelab.dev/missions/

Take responsibility for a customer deployment. Inspect evidence, choose an approach, review its consequence, and leave a service the customer can operate. All names, messages, timings, and outcomes are fictional.

[Play Deployment Run](https://fdelab.dev/#game)

## Your three customers

### The Monday queue

Northstar Services — Dispatch operations

Get repair requests to eligible technicians faster. Every assignment still needs a dispatcher’s approval.

[Read the Northstar Services mission brief](https://fdelab.dev/missions/northstar/)

### The missing invoice

Cedar Supply — Finance operations

Reduce invoice matching work. The pilot may create draft matches; payments and bank-detail changes stay outside its authority.

[Read the Cedar Supply mission brief](https://fdelab.dev/missions/cedar/)

### A very confident answer

Harbor Engineering — Internal knowledge

Help staff find the right procedure faster. Preserve source authority, current versions, and each caller’s access.

[Read the Harbor Engineering mission brief](https://fdelab.dev/missions/harbor/)

## What a delivery must prove

- Finish five decisions within 14 simulated days. There is no real-time timer.
- End with customer trust of at least 60 and reliability of at least 70.
- Recover the incident and demonstrate handoff to an owner and backup.
- A smaller supported service or controlled pause can count as a successful delivery.
- Only the best result for each mission contributes to campaign XP.

[Read the full scoring and provenance notes](https://fdelab.dev/research/deployment-run.md)