Skip to content

Domain Pressure to Mission Conversion Playbook

Overview

Domain pressure should generate playable work, not remain abstract setting drift. This playbook converts regional conflict, resource shocks, and polity maneuvers into immediate mission structures that parties can pursue at adventure scale.

Core Pattern

Use a five-step conversion chain:

  1. detect a pressure spike
  2. identify actors and stakes
  3. generate a mission frame
  4. attach constraints and consequences
  5. feed outcomes back into domain state

The loop prevents domain play from splitting away into a separate minigame.

Standard Procedure

  1. Select one advancing domain pressure (governance, security, infrastructure, belief, or resource control).
  2. Name the two to three actors whose interests collide at this pressure point.
  3. Choose the mission objective that best expresses the conflict (retrieve, protect, infiltrate, sabotage, investigate, escort, cover up).
  4. Assign one location and one active condition from current world response signals.
  5. Publish the mission as rumor, contract, plea, or threat.
  6. After session resolution, adjust faction posture, clocks, and settlement services.

Why It Works at the Table

  • Keeps macro campaign motion visible to players.
  • Produces missions with clear stakes and context.
  • Reduces prep by reusing existing pressure data.
  • Makes mission fallout matter beyond one session.

Conversion Rule

Each domain pressure event should generate at least one of:

  • a paid job
  • an urgent defensive action
  • a diplomatic or espionage objective
  • a denial mission against a rival move

If pressure does not produce actionable work, it is not yet integrated into play.

Constraint Rule

Attach one mission condition directly from world state:

  • supply shortage
  • patrol escalation
  • blackout or infrastructure instability
  • rival team deployment
  • political deniability window

Conditions create friction that reflects domain reality.

Fallout Rule

Mission outcomes must update macro state:

  • faction heat shifts
  • service access volatility
  • changed rumor stream
  • clock advancement or rollback
  • new opportunity or retaliation chain

Without this feedback, conversion becomes one-way and loses campaign coherence.

Referee Procedure

  1. Keep a short list of active pressures and nearest crisis thresholds.
  2. Convert only top-priority pressures into session-facing work.
  3. Offer at least two mission vectors when possible (aligned and opposed).
  4. Publish consequences before revealing all causes.
  5. Log post-mission changes in faction and settlement turns.

Design Guidance

  • Avoid missions detached from current pressure clocks.
  • Use actor goals to differentiate otherwise similar objectives.
  • Let failed missions create new conversion opportunities.
  • Keep mission framing concrete even when stakes are strategic.

Practical Comparison Rule

Use this playbook when domain and faction dynamics should directly shape session agendas. Use stand-alone mission generation when campaign macro state is intentionally light or static.

See Also