Content Brief and Action Center workflow
Turn retained provider evidence into a reviewable implementation task.
From measured question to Content Brief
Create SEO task
From a measured AI Visibility recommendation, choose Create SEO task. The task stays linked to its source Provider Run and exact customer question.
Open Content Brief
Open the task target from AI Visibility or Action Center. The brief shows the stored answer, brand and domain evidence, attributable alternatives and citations, required changes and acceptance criteria.
Choose the implementation path
An Aetherion Project can use Open Builder + copy brief or Generate content draft. A site without writable source uses External Website · manual implementation.
Review the exact result
For a generated project change, inspect every file in Pending Change. Choose Apply only when the diff preserves the existing design and uses verified first-party facts; otherwise choose Decline.
The brief is deterministic
Opening a Content Brief builds it from the retained provider run and task evidence. It does not make another AI request. Generate content draft is a separate, billed Builder action.
Read the task status correctly
| Status | Meaning |
|---|---|
| Open | The measured opportunity exists, but implementation work has not started. |
| In progress | The user is preparing or reviewing the change. |
| Applied | A reviewed Builder source change was applied. This is a source checkpoint, not a public release. |
| Awaiting deployment | The public verifier cannot yet prove a newer production release, or the latest manual package was declared published but still needs complete live evidence. |
| Ready to retest | The public implementation passed deterministic verification and can be sent to the provider again. |
| Verified | The provider retest recorded real before → after improvement for the measured brand or domain evidence. |
Applied is not deployed
Apply updates source and records an implementation checkpoint. It never proves that the public website changed. Verified is also not a manual status; only the provider retest can set it.
Start another iteration
If the live check or provider retest does not confirm the intended result, reopen the task from Action Center. Reopening clears the previous implementation checkpoint and public verification so an older deployment cannot validate a newer change. The original provider baseline remains available for a valid later comparison.
Need project-specific help?
Open the private Help Center or create a support ticket with the affected project, route and request ID.