Assisted and Full
The two automation modes, what each one does unattended, and why Full is not a way around review.
Autopilot has two automation modes. The difference is where a run stops.
| Assisted | Full | |
|---|---|---|
| Selects Topics | Yes | Yes |
| Researches and drafts | Yes | Yes |
| Places images and internal links | Yes | Yes |
| Leaves posts for review | Yes, always | Where the Direction requires it |
| Schedules posts | No | Yes |
| Publishes posts | No | Where the Direction allows it |
| Replenishes its own Topic supply | No | Yes, on by default for a new setup |
Assisted
Assisted prepares work and stops. Every post it produces waits for a person, regardless of what the Content Direction says.
This is the mode for a blog where you want the writing done but the judgement kept. It is also the right mode for the first few weeks of any Project, because it shows you what the pipeline produces before anything is public.
Full
Full can carry a post all the way to your public blog, but only where the Content Direction allows it.
What that consent covers
With it on, Full may publish past five holds: the Direction's own review requirement, a quality review, a risk review, an unacknowledged risky automatic lane, and an image review.
Four narrower consents sit underneath it and apply only while it is on: publishing when facts could not be verified, when sources are missing, when a detector says part of the article is invented, and when image generation failed. For a new Full onboarding setup, facts, sources and image failure start on while the fabricated-content exception starts off. Each remains separately visible and can be changed before activation. Turning the parent consent off takes every nested exception with it.
What it never covers
Some holds cannot be consented away:
FOUNDER_APPROVAL_REQUIRED, so a Direction on the legacy founder policy always waits for a person.CONTENT_CHANGED, where the article moved after it was approved.IMAGE_GENERATION_PENDING, and any malformed approval, quality, image or risk state.
So the real question is not "which mode" but "which Directions do I trust to publish without me, and have I turned that consent on".
Topic supply
Full mode can additionally replenish its own Topic supply, so a Project does not run dry between reviews. Blogged writes new Topics from your approved Content Directions and works through them without asking you to approve each one.
It is still authorised separately from drafting, and it is still Full only. A Project that has already saved a configuration keeps whatever it stored rather than being moved onto the new default, and an older or malformed stored value resolves to off. Switching a Project to Assisted turns refill off with it.
The alternative, existing approved Topics only, means exactly that: planning waits when no eligible Topic remains, which is the right setting when you want to decide what gets written.
Switching modes
Switching applies to work from that point on. Posts already waiting at a gate stay where they are.