Autonomy works best when the setup is explicit. Your site's operating policy tells Sutra which work to attempt, when to run it, and where to stop.
Choose the right amount of autonomy.
Check only reads your website and suggests improvements. Prepare drafts creates content for review. Autopilot allows eligible scheduled work to progress within the site's policy.
Choose a mode for each site. One client may be ready for more automation while another still needs close editorial review. A shared workspace does not require the same policy for everyone.
Make the limits concrete.
Set a daily AI allowance. Autopilot schedules a daily work cycle. Enable publishing only when the destination is connected and you want the agent to be able to publish under that site's policy.
Publishing permission is a separate decision from producing a draft. Content still has to pass the applicable quality checks. Unsupported claims and failed reviews can stop the work before it reaches the site.
- Choose the operating mode for this site
- Set a cadence and a daily allowance
- Decide whether publishing is permitted
- Keep the site's verified brand facts current
Follow the record when something needs you.
The activity history shows what ran and which work needs attention. A published post has a recorded result. Content that cannot proceed stays available for inspection instead of being counted as a successful outcome.
Read the evidence alongside the summary. A completed inspection is an operational result; a change in search performance is a separate observation. A single model answer is a sample at a point in time.
Leave room to change direction.
Pause a site when circumstances change. Review pending work, update brand memory, or adjust the policy before resuming.
Pausing affects upcoming actions. It does not undo work already published. Use the publication record and available rollback controls when a published item needs to be reversed, and verify the destination afterward.
A useful next step
Explore operating policies