Skip to content
Arka Platform

Frame a mission with Mission Control

Mission Control in arka-deck is centered on Mission Guardian and its active guardian pack. The pack carries the flowmap, mode rules, event policy, UI cards, tool policy and runtime injection layers for the project.

Mission Guardian — when the agent cannot proceed

Section titled “Mission Guardian — when the agent cannot proceed”

For a structured mission (squad or phase chain), Mission Guardian lets you define:

  • The phases the mission must traverse (e.g. Analysis → Plan → Execution → QA → Delivery).
  • The evidence expected at each phase (a report, a QA verdict, etc.).
  • The gates: an agent cannot move to the next phase until the evidence is present and validated.

Mission Control view in the project: active guardian pack, current workflow, UI validation cards, role policies and runtime injection previews.

Step-by-step configuration

Section titled “Step-by-step configuration”
  1. Open the project’s Mission Control view.
  2. Review the active guardian pack.
  3. Check the workflow, modes, validation cards and role-specific tool policy.
  4. Use the chat side panel to follow the current mode, next gate and expected documents.
  5. Validate cards from the UI when a transition needs an explicit user decision.

Followup

Section titled “Followup”

Relevant mission events feed the Mission Control state: decisions, actions, risks, deliverables, blockers, QA verdicts and audit trail. Agents receive a role-scoped runtime packet rather than a generic wall of rules.

Public boundaries

Section titled “Public boundaries”
  • Mission Guardian is in beta — automatic report integration is still being hardened.
  • No autonomous rule invention. arka-deck does not invent rules; it applies the guardian pack materialized for the project.

Going further

Section titled “Going further”