# The Monday queue: an FDE dispatch operations simulation

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

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

Northstar Services is a fictional customer. Your contact is Maya Chen, dispatch lead.

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

[Play or resume this mission](https://fdelab.dev/?mission=northstar#game)

## Your first conversation

We spend 18 minutes routing a request. The sponsor wants an AI demo by Friday. I need something my dispatchers can actually use on Monday.

## Evidence to inspect

Five recent requests: Most time was spent checking technician eligibility, not classifying the request.

Access: Eligibility records live in three systems. Write permissions are not confirmed.

Acceptance: Maya will accept the pilot. A dispatcher must approve every assignment.

## Five decisions in the engagement

- Discover: Discover the expensive handoff before choosing what to automate.
- Connect: A retry needs a stable business identity and a known write boundary.
- Evaluate: Test the resulting workflow, including the checker and the operator’s review effort.
- Recover: A missing response is not proof that the operation failed.
- Hand off: Ownership is demonstrated by the receiving team, not transferred by sending a document.

## Delivery gates

- 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.

[Explore all three missions](https://fdelab.dev/missions/)

[Build the underlying skills](https://fdelab.dev/learn/)