Recommendations and delivery to your MCS
A recommendation is a change a workflow suggests for a pass, with what it gains in the low case and when it must be decided by. Whether it reaches your mission control system (MCS) as advice, waits for a person, or is only recorded depends on the workflow's policy step and your plan. Act is the part of the Operator + Act plan and above that lets a recommendation be sent to your MCS as an instruction; on plans without it, recommendations are advice only.
What a recommendation says
| Part | In the API | Example (illustrative) |
|---|---|---|
| What to change | action.verb: swap to a backup pass, or reroute off a link | Swap to Troll |
| What it gains | action.gain_gb_p10: the GB it keeps in the low case | +3.2 GB in the low case |
| When to decide | action.deadline, such as a provider's cancel deadline | Decide by 10 Nov 12:02 UTC, in 2 h |
rain-fade-swap suggests swaps for passes whose weather could cost too much. rfi-watch suggests reroutes from the rfi lane. See The template catalog.
Show, send or trial
Every recommendation on a result carries a mode, and the Platform names it:
mode | On screen | What reaches your MCS | When |
|---|---|---|---|
suggest | Advice | Show: the recommendation rides on every output as advice, for an operator to act on in the MCS. Nothing waits on approval. | A run that delivers, on Operator + Act, with no policy step or a policy step in suggest mode |
approve | Pending, then Followed, Declined or Expired | Send: nothing until a person approves it. Approving sends it again as an instruction for your MCS to carry out, and the item says action_status: approved. | A policy step in approve mode, on a run that delivers, on Operator + Act |
shadow | Trial, or Test run | Trial: nothing. Shadow means the run records what it would have sent and sends nothing. | During a trial (shown as Trial), and on a test run on Operator + Act (shown as Test run) |
off | Not sent | Nothing. The run keeps what it would have done on its own items, as advice for an operator. | Any run on a plan without Act. The workflow's recipe reads Each recommendation shown as advice, and its plan reads Advice on Operator · approvals need Operator + Act (on Explore, Advice on Explore). |
A delivery mode that lets your MCS carry out a recommendation with no person deciding is not available yet: every instruction is approved by someone first. Moving a workflow from trial to sending is a guide of its own: From trial to sending.
Deciding one
Under Upcoming on Passes, Waiting on you counts the recommendations held for a decision. Open a pass to see what it recommends, its gain in the low case and its deadline, then choose Send to MCS (Followed once it is sent) or Decline; each asks you to confirm. Decided recommendations, and what a trial recorded, are under Past on Passes.
The rules are the API's, wherever you decide:
- An approval cannot be undone. A declined recommendation cannot be decided again.
- A decision belongs to the workflow and the recommendation, not one run: the next run that suggests the same change on the same pass carries it.
- A recommendation left undecided expires at its deadline, or at the start of its pass (the end of its span, for a link) when it has none, and nothing is sent for it. Once a newer run or a newer version of the workflow answers it, it can no longer be approved.
- Approving needs Operator + Act and the
act:approvescope. Declining needs the same scope, on any plan. On Passes your sign-in holds it; over MCP or the API, a live key with it does. - Declining takes no reason yet: the API has no field for one.
In the API, read held recommendations with GET /predictions/actions?workflow=<slug> and decide them with approve or reject; see Held actions. An AI agent can do the same over MCP with list_actions, approve_action and reject_action.
How it reaches your MCS
A connector in your network pulls each run's workflow results from Constellation and writes them into your MCS: Yamcs, OpenC3 COSMOS, Anduril Lattice, Open MCT, or your own system. An approved recommendation arrives as an item with action_status: approved; carry it out before its deadline. See Connectors and the results protocol.