Current Plan
This page owns the synthesized "what matters now" layer above the raw queue.
Role
The Current Plan surface should answer one question quickly: what is the player or settlement most likely to care about right now across planning and execution?
It sits above the Objectives and Queue screens: Current Plan summarizes, Objectives explain, Journal preserves durable memory, and Queue executes. It rolls up the urgent objective, the relevant clues, the active mission and composed activity approach when one exists, the most relevant Journal memory when a thread needs readback, and the activities currently executing or blocking that work.
Inputs
Current Plan summarizes:
- urgent objective and clue pressure
- active mission state
- linked Journal context when the player needs a prior discovery, day note, or written interpretation to understand the current pressure
- active composite or routine activity context when the player is using a recognizable composed approach
- queued, executing, and blocked activities
- character readiness
- settlement shortages or risks
- nearby leads, threats, or time-sensitive opportunities
Queue State Vocabulary
Current Plan and Queue share a single canonical queue-state vocabulary, defined in gd-queue-screen.md § Queue State Vocabulary. The six states are Running, Queued, Blocked, Preview, Suggested, and Scheduled-Repeat. Current Plan surfaces the Running and Blocked states most prominently because they answer the "what is advancing the urgent thread / what is blocking it" question; it must not invent local synonyms for those states.
The route preview overlay is a shell-level concern owned by the map and the Location dossier. Current Plan does not surface route previews; it surfaces the travel activity once it has been committed to the queue.
Design Rules
- Current Plan summarizes; it does not replace the queue or objective screens.
- Current Plan may quote or spotlight a Journal entry, but Journal owns durable reread and day-based history.
- Every surfaced plan item should be traceable to a real objective, clue, mission, activity, shortage, threat, or world fact.
- Urgency should stay legible without hiding why something is urgent.
- The surface should make it obvious which queue activities are advancing the urgent thread and which ones are blocking it.
- Queue-state wording must match the canonical vocabulary in
gd-queue-screen.md.