-
Notifications
You must be signed in to change notification settings - Fork 0
Mission Control and Ops
The ◎ OPS tab answers the eternal question: "I have 90 minutes — what's actually worth starting?" Plans, objectives, learned timings and shared boards all stay on your machine.
Tell it your time available and press BUILD SESSION PLAN: Frameshift ranks your known work — active missions (expiry-aware), pinned engineering steps, cargo to sell, colonisation hauling, Powerplay context — by urgency, value, risk and whether it fits your window, and returns an ordered, plot-ready list with time estimates and dependencies ("buy before you can deliver").
The time estimates aren't guesses: Frameshift learns your pace from your own journal — how long your dockings, jumps, mission turn-ins and mining runs really take, menus and mistakes included. A fresh commander starts with deliberately padded defaults; the more you fly, the sharper your plans get. The card shows how many personal timings have replaced the defaults.
Durable per-commander to-dos with category, priority, optional system/station/body, deadline and time estimate — "deliver tritium to the carrier", "unlock Ram Tah before the weekend". They persist across restarts and feed the session planner alongside everything journal-derived.
A shared board — objectives, assignments, resource reservations, contributions — that works without any service: export it as a JSON file, share it on Discord, and merges are deterministic when it comes back. Nobody creates an account; nothing leaves your machines except the file you chose to share.