5.4 · Polish and publish

Polish is the step where you get your hands on the text. Review was annotation-only by design; Polish is the opposite: a full editor where you can line-edit every sentence until the article reads exactly the way you want it to ship. Use it for the final-mile tweaks that are about your taste and your brand comfort, the edits you would otherwise make in a Google Doc on the way out the door.

One thing to know up front: Polish is not part of the training loop. Edits here ship with this article and teach nothing. If you find yourself fixing the same thing in Polish on every article, that is a pattern that belongs in Review as an annotationAnnotationA note you leave on a draft saying what is off and why, instead of silently rewriting it. Annotations accumulate as pending feedback and fold into your writing profile when someone clicks **Update profile**. Annotating is what teaches the next draft; editing is not., a note saying what is off and why, or in your Writing ProfileWriting profileThe compiled version of how you sound. Every draft starts from it, and it is the only place annotations become voice: pending feedback folds in when **Update profile** is clicked., the compiled version of how you sound, where fixing it once fixes it forever.

Polishing

The Polish editor works like the context editor: autosave, versions, one editor at a time. If you arrive with unapplied Review notes, the editor stays locked until you apply them, so hand edits never collide with a pending rewrite.

2 agentAgentAn automated worker inside GrowthOS. Agents research your market, propose opportunities, write drafts, and score the pages you already have. Every agent stops at a proposal: nothing publishes and nothing moves forward until you review it and decide. assists (automated helpers) are available when you want them:

• Quick edit: select text, click AI, and describe a change or pick a preset (Humanize, Tighten, Break up the wall, Match our voice, Answer first, Fix grammar & spelling). It is stylistic only, and says so itself: no research access, so it cannot add new facts, stats, or sources.
• Auto-improve Coverage: one click against the coverage rubric, for gaps you would rather not hand-write.

When the article reads right, move to shipping.

Title and meta

Adjust title & meta controls how the page reads on the page, in Google, and when shared: article title, meta title (60 characters), URL slug, meta description (160 characters), and the cover and social image, all with live previews of the Google result and the social card. Each field can be regenerated individually if you want another take. Give the slug a deliberate look here; it becomes the page's address.

Publishing

The Publish step offers the paths, and which you use depends on your setup:

Publish through a connected CMS

If your workspaceWorkspaceEverything GrowthOS knows and does for one brand. Every figure, page, and agent in your workspace covers that brand only. (everything GrowthOS knows and does for your brand) has a CMS connection, your GrowthX strategistStrategistYour GrowthX contact: the person who configures your workspace, runs the parts of the product that sit outside it, and takes the corrections only you can catch., your GrowthX contact, can push everything (body, slug, meta, cover) straight into your CMS as a draft. That card is GrowthX tooling, so you may not see it yourself. Going live stays a separate, explicit choice: take your final look in your own CMS, then publish there. Your own 2 paths on this step are the agent handoff and Mark as published.

Or publish via your agent

The Publish with Claude card (or Claude Code, or Cursor) hands the briefBriefThe plan for one page: the research, structure, and targeting a draft is written from., the working record the page was built in, to your AI agent: it fetches the article from GrowthOS over MCP and drafts it into your CMS through your CMS's own integration. Drafts only, always: the agent never publishes anything live directly. This is the path when your CMS is not directly connected, and it requires your CMS's MCP configured on your agent.

Confirm it's live

A brief becomes Published when a live CMS publish is confirmed, or when you paste the live URL into Already shipped it? and mark it published. Either way, always open the live URL and read the page where your buyers will. The brief keeps a View live page link from then on.

There are also escape hatches for any other workflow: Copy as markdown for the article body, or Export bundle for everything (article, meta, cover, schema) as a file.

Your first published page

Publishing the first one is a milestone. Read it live, share it internally, and then go straight back to the well: the fastest teams publish their second page the same week, because the loop (pick, create, review, publish) builds skill through repetition, not contemplation.

Common questions

Why doesn't publish go live in one click? Because your CMS is the source of truth for your site. Draft-first means your existing review gates still apply, and nothing appears on your domain without an explicit decision in a system you control.

I made heavy Polish edits. Do I tell the system? The shipped article stands as you shipped it. But if the edits reflect standing preferences, spend 2 minutes turning them into Review-style feedback on the next article, so the training loop hears what your hands have been fixing.