Content Work
Content Work adds revision review to content engagements. Existing Routines remain the repeatable workflow feature at their current routes.
Open Clients, then Open content work. A current organization administrator with project CMS edit permission can save an article, template, redirect, revert, brief, topic map, findings, baseline or report artifact. These drafts use native artifact storage and retain earlier versions. Choose Me or a current organization member as the approver; the server also requires that person's current project access.
The chosen person opens the draft, reads the exact content and chooses Approve reviewed revision. Approval covers its revision, title, stored content fingerprint, engagement revision and chosen person. A subsequent edit needs another review. Removed access and expired approval prevent preparing work. Clients without draft permission see their review controls.
Prepare approved work records one intent with an unknown execution outcome. It does not publish or send content. Repeating the same request preserves the intent. A later revision cannot replace an unresolved earlier intent. Effect execution and reconciliation are still pending integration; an unknown outcome must remain unknown.
SEO findings and baseline artifacts validate their declared formats. Findings retain phase and page identity, scoring and unaudited coverage. Missing measurements remain null, while a recorded zero remains zero. SEO evidence shows retained approved baseline revisions, including their original bytes after an edit or approval expiry. Historical approval is evidence; current work still needs current approval. Administrators with CMS edit permission can use Record manual SEO check to record the observed result, source, observation time and freshness expiry. These records are labelled human observations. Missing checks stay unknown and expired observations show stale; agents and clients cannot record a human check. Source text is data and cannot grant approval or change the target organization.
Agent abilities
Remote and stdio MCP expose list_content_work, get_content_work, draft_content_work, edit_content_work and get_content_seo_state. Both use the same request schemas and real permissioned REST routes. Supply the current organization and engagement IDs; reads include the source's revision. Draft creation requires a stable idempotency key. Agent credentials cannot mint the selected person's approval, and no approval or publication tool is provided in this group.
A CMS-only organization key discovers these abilities through GET /v1/content-work/status; it does not acquire the orgs or native artifacts resource family. The organization-specific availability route is GET /v1/orgs/{orgId}/content-work/status. CONTENT_ENGAGEMENTS_ENABLED controls these additive routes; no production configuration change is part of this implementation.
No client price is quoted as agreed. The Clients page labels proposed prices for administrators; client plan and content work readbacks exclude the private price and internal budget.
Content execution, provider metrics, crawl provenance, editorial CMS linkage, remediation receipts and monthly report generation are pending. Native draft/read/approval tests do not prove those dependent workflows or a production rollout.