Missions: give AMOS an outcome

A Mission is how AMOS turns a plain-English outcome into bounded autonomous work. You approve a contract once, and the result has to pass an independent check before it counts as done.

How a Mission works

1. You state the outcome. In plain words: the result you want, what it may spend, what it must never do, and what to ask you about first.
2. AMOS compiles the contract. The platform turns your ask into an exact Run Contract (budget ceilings, the operations it may use, hard boundaries, and the checks that must pass) and shows it to you for one approval.
3. It works inside the lines. The Mission plans and acts on its own within the contract. If it hits a boundary you set, it stops and asks instead of guessing.
4. Independent verification. A separate checker, not the model that did the work, verifies the outcome before the Mission can call itself complete.

Missions on the Free plan

• Three Mission starts in any rolling 30 days, with one Mission running at a time.
• A free Mission can work with your AMOS data and the business systems you have connected, but it cannot create standing automations or use AMOS-hosted infrastructure such as app deployments.

Paid plans include more Missions each month; see Pricing and plans.

Staying in control

You can pause or cancel a Mission at any time, and every action it takes leaves a receipt.