# Audit and improve an article

> GrowthOS browser-agent journey: Content Quality Agent

## Contract

- Journey ID: `content-quality`
- Availability: `available`
- Risk: `credit-consuming`
- Entry URL: `/dashboard/writer/articles`
- Interface: authenticated browser session

## Objective

Evaluate a saved article, explain issues by severity, and prepare revisions without silently overwriting editorial decisions.

## Successful outcome

A content-quality result tied to the saved article, with actionable improvements and a recheck path.

## Prerequisites

- The correct client is selected.
- A saved article exists in GrowthOS.
- The user has identified which article should be reviewed.

## Inputs

- Saved article
- Optional quality objective or editorial constraint

## Browser steps

1. **Open the article.** Find the requested saved article and verify its client, title, and latest content.
   - Expected: The intended article is open.
2. **Prepare the audit.** Select the content-quality action and review any displayed scope or credit information.
   - Expected: The requested review is ready for approval.
3. **Request approval.** Ask the user to approve the content-quality run if credits will be consumed.
   - Expected: The user explicitly authorizes the audit.
4. **Run and wait.** Start the review once and wait for every quality section to complete.
   - Expected: A complete quality result is attached to the article.
5. **Explain the result.** Summarize score, severity, affected sections, and suggested corrections.
   - Expected: The user understands what is deterministic, suggested, or editorial.
6. **Apply only approved edits.** Propose revisions and wait for approval before changing article content.
   - Expected: Editorial judgment stays with the user.

## Approval boundaries

- **Before a credit-consuming audit:** The user approves the displayed cost.
- **Before changing article content:** The user chooses which revisions to apply.

## Outputs

- Quality score and status
- Issues grouped by severity
- Affected sections
- Recommended revisions
- Recheck option

## Recovery

- If results look incomplete, confirm every audit section has reached a terminal state.
- If the article changed after the audit, run a new review only with user approval.
- Preserve the original text until edits are approved.

## Guardrails

- Never run a paid quality audit without explicit user approval.
- Never silently rewrite an article.
- Never publish as part of the quality-review journey.
- Distinguish suggestions from verified facts.
- Do not reuse a quality score for content that has changed.

## Copyable prompt

```text
Open GrowthOS using my authorized browser session. Find the saved article “[ARTICLE TITLE]” for the selected client and prepare a Content Quality review. Show me any cost before running it. After I approve, wait for all review sections to finish, then summarize the score, severe issues, affected sections, and recommended revisions. Do not edit or publish the article without another explicit approval.
```

## Related journeys

- [writer](/agents/writer)
- [seo-audit](/agents/seo-audit)
- [safety](/agents/safety)
- [errors](/agents/errors)