Skip to main content

Objectives Screen

This page owns the player-facing workspace for clues, missions, objectives, and important discoveries, with links into the persistent Journal when discovery or memory context matters.

Role​

The Objectives screen should tell the player what matters and why.

It is the planning workspace for the high-level stack: objective first, then clues, missions, and any composed activity approach the player is using to pursue them. It should also surface the Journal entries that record how the MC understands those threads without turning the screen into a prose log.

It sits below Current Plan and above Queue: Current Plan summarizes what matters now, Objectives explains why it matters, and Queue carries the atomic activities that execute it.

It Should Show​

  • current objectives as high-level goals or arcs
  • unresolved clues or leads, with clue uncertainty kept visible
  • active missions
  • journal-linked discoveries or prior day entries when they materially explain why a clue, mission, or location now matters
  • active composite or routine activity shapes where a mission or recurring routine has a recognizable composed approach
  • recent discoveries with strategic consequence
  • direct links into Locations, sites, actors, and the queue activities the player may need next

Design Rules​

  • Keep uncertainty visible when a clue is only partial.
  • Show strategic context, not only a flat todo list.
  • Let the Journal own long-form rereadable prose. Objectives should show the planning consequence and link back to the relevant Journal page when memory or interpretation matters.
  • Do not let composite or routine activity labels replace the underlying mission or activity detail. The screen should explain the structure, not hide it.
  • Let the player drill into the queue or dossier from any important row.

Map Navigation From Objectives​

Location links inside Objectives route through the canonical map interaction contract documented in gd-shell-screen-model.md § Map Interaction Contract. A Location chip click is equivalent to a left-click on that Location on the map: it selects the Location and updates the compact or wide panel state. Double-clicking the chip is equivalent to a double-click on the Location (focus, zoom, open the full-mode planning board). Objectives does not bypass the canonical interaction contract with a dedicated drill-in surface.