Problem + ignored cost
Teams miss qualified topics or publish disconnected AI drafts. The cost is lost demand, editorial rework and content that never reaches production.
Use case · content growth
The Content Growth Agent owns research and drafting; the Site Experience Engineer owns implementation; a human owns editorial and production approval.
OUTPUT PACKET
Teams miss qualified topics or publish disconnected AI drafts. The cost is lost demand, editorial rework and content that never reaches production.
A scheduled gap review, product launch or human request is scored by the Supervisor and assigned to Content Growth.
SERP/query observations, site inventory, primary sources and Brand DNA become a brief, draft, media notes and implementation proposal.
Approval to measurement
Qualify intent and avoid existing-page collision
Evidence, owner and next state remain visible.
Prepare sources, entities, outline and conversion role
Evidence, owner and next state remain visible.
Draft content and original media requirements
Evidence, owner and next state remain visible.
Editor reviews accuracy, voice and usefulness
Evidence, owner and next state remain visible.
Engineer validates route, metadata, links and build
Evidence, owner and next state remain visible.
Human publishes; baseline window measures discovery and conversion
Evidence, owner and next state remain visible.
The reviewer sees sources, full content diff, preview, expected impact, risks and validation. Rejecting returns specific revision notes.
GitHub uses a protected proposal branch/PR; WordPress uses a governed change card. Agents cannot self-publish.
Indexing, queries, engagement and conversion are observed without guarantees. Starter fits lower cadence; Growth fits a serious monthly calendar.
Paid deployment · human authority
Choose a paid plan, establish the baseline and reserve content capacity before activating the workflow.