What it's for. Build and track Expundeus contracts using the DM Bible template. Every mission separates what the players are told from what's really going on, and forces you to write all three ways it can end before you run it.

How to fill it in

• Mission ID — auto-fills as the next SC-NNN; editable.
• Region / Status — where it happens and where it sits in its lifecycle.
• The Brief — what the contractors are told at assignment.
• True Objective — what's actually happening underneath (DM eyes only).
• Complication — the twist or pressure that makes it more than a fetch quest.
• The three outcomes — Full Success, Partial/Compromise, and Failure/Refusal.

The three-outcome rule

Save stays disabled until each outcome has at least 20 characters. This is deliberate — the DM Bible discipline is that you write the failure state before you run the mission, so you're never improvising consequences at the table.

Status lifecycle

• Seeded — written and available to assign. Active — players are on it. Escalated — ignored or worsened; the world is reacting. Closed — resolved.

Seeded and Active/Escalated missions automatically populate your Session Prep sheet. Use the Thread Entries box (one per line) to jot developments as a mission runs.