What problem does it solve? Agents working with the aops CLI need clear rules for managing hosted Agentspace missions—creating them, seeding policy, resuming sessions, and keeping ownership boundaries straight between Mission, Projectman, and Memory. ## Core Features & Use Cases - Mission Command Map: Provides exact commands for mission create, list, get, update, resume, and the start --resume bridge with JSON output flags. - Policy Seeding: Explains how to pass the policyJson emitted by aops-cli start into mission create and update calls using the working-discipline convention. - Ownership Boundaries: Defines which system owns execution truth (Projectman), durable context (Memory), and decision truth (Discuss), with explicit anti-patterns to avoid. - Use Case: An agent resuming a long-running project runs aops-cli mission resume with a mission id to get a compact, token-efficient pack of active plan refs, review refs, and session guidance before continuing work. ## Quick Start Ask the agent to create an aops mission with an objective and the policy JSON from aops-cli start, then resume it later with aops-cli mission resume.