# AUTOMATIONS: Work that keeps running with a reason.

> Turn a repeated outcome into a scheduled or persistent Mission, keep its context attached, and notify people only when something changes or needs attention.

- Canonical page: [/solutions/automations](https://grain.sh/solutions/automations)
- Agent-readable page: [/agents/solutions--automations.md](https://grain.sh/agents/solutions--automations.md)
- Section: Solutions

## What this page covers

- Output: Recurring Mission
- Output: Change summary
- Output: Exception alert
- Output: Audit trail
- Stay quiet when nothing changed: Avoid notification noise by surfacing meaningful changes, failures, and decisions instead of every poll.
- Keep context between runs: Use the same objective, references, and owner controls so recurring work remains consistent.
- Escalate to a person: Pause for approval or direction when the automation reaches a boundary that requires judgment.
- Start with the outcome: Describe what should be true when the work is done. Grain turns that outcome into a visible Mission.
- Bring the right engine: Use hosted Grain Models or route execution to supported models and CLIs on your connected machines.
- Inspect, edit, and ship: Review the result in Grain, ask for changes, and keep a person in control of the final action.

## Why it matters

Grain automations remain visible Missions. You can inspect what happened, ask for a change, and adjust the routine without rebuilding it from scratch.

## About Grain

Grain is a multi-agent work platform. A person describes an outcome as a Mission, Grain coordinates the models, tools, files, repositories, and connected computers needed to do the work, and the result returns for review.

Start with [the complete agent-readable index](https://grain.sh/agents/index.md) or read [the full site corpus](https://grain.sh/llms-full.txt).