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 structured 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, memory record, 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
Dynamic Pressure Ranking
When dynamically generated mission candidates, urgency scores, or ignored-pressure consequences rank into Current Plan, each item must be traceable to a specific source fact: the Feature transition, taint escalation, settlement shortage, route danger, faction claim, or character state that caused it. An urgency item without a visible source fact is a contract violation. The full ranking and traceability rules are documented in ../systems/gd-dynamic-quest-pressure-model.md under "Urgency Signal Contract".
Activity Detail Cross-Reference
Activity links surfaced in Current Plan — the chip on the active mission, the
linked activity for an urgent objective, the running-activity readback — are
canonical openers for the shared Activity Detail inspector defined in
gd-shell-screen-model.md § Activity Detail.
Opening an activity link from Current Plan passes planning opener context to
Activity Detail: source surface 'plan', the activity def id, and the
associated objective reference when present. Current Plan does not own the
Activity Detail inspector — it is one of the canonical openers, alongside
Queue, Territory Dossier, the Activity Catalog, Objectives, ContextPanel,
BottomQueueSlots, and Journal. Current Plan does not own activity execution;
the inspector's queue commands route through the canonical queue path.
Example: when the Survive thread is urgent and the water mission is active, a
ListenForWater chip appears next to the mission state. Clicking the chip
opens Activity Detail with source: 'plan', the activity def id for
ListenForWater, and the Survive objective reference. From there the player
may queue the activity, drill into a child run when one exists (the parent-run
reference field Wave B exposes — Wave B-owned, pending sync), or close back to
Current Plan with planning context intact.
State Gate Rule
Current Plan refreshes when state gates, blockers, or risk surfaces change. A new day header alone does not promote a thread. If the player camps, trains, or repeats routines for several days while the same mission state remains unresolved, Current Plan should keep surfacing that unresolved state rather than silently jumping ahead.
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 Territory 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. - Day change alone must not create a new plan state.
Implementation status
| Surface / Behavior | Shipped wave | Status |
|---|---|---|
| Current Plan synthesized "what matters now" surface | Deferred | Current Plan is not yet a first-class screen component; the synthesis layer is described as the design intent above |
Activity link chip → Activity Detail (source: 'plan') opener | Deferred | Requires Current Plan to ship plus the objective-to-activity link chip; example marked illustrative |
| Recursive drill-stack reachable from a plan-origin Activity Detail | Deferred, Wave B | Requires parent-run / child-run reference projection on the activity run snapshot — Wave B-owned, pending sync |
Queue-state vocabulary alignment with gd-queue-screen.md | Wave C | Vocabulary canonicalized; Current Plan must not invent local synonyms |