# Agent Composer Overview

Building a WordPress site is a defined project, but operating its content continues after launch. Agent Composer lets agencies turn an existing site's content types, patterns, and editorial rules into governed workflows that compatible AI agents can use to create validated Gutenberg drafts.

The agency or site builder remains responsible for the original design, theme, patterns, content types, and editorial model. Composer owns Site Contracts, page-type Blueprints, validation, draft ownership, audit, and the execution boundary. The active theme owns templates, patterns, `theme.json` presets, and final rendering. Changing a theme does not silently import or activate configuration.

The configuration hierarchy is `Config Set -> Site Contract -> Blueprints`. A Site Contract contains site-wide editorial, structural, media, and design policies. Each Blueprint maps a stable page type to an allowed post type, template, patterns, blocks, required sequence, excerpt policy, and validation constraints.

After the official WordPress MCP Adapter is active, an authenticated client can load configuration and design context, list approved patterns, resolve approved relation targets, use policy-approved taxonomy terms, validate a plan, create or update an agent-owned draft, and obtain a preview. Composer is the controlled WordPress execution layer, not a general-purpose AI model or website builder. The user keeps reasoning and model access in ChatGPT, Codex, or another compatible client.

The recommended execution identity is a dedicated WordPress user with the `smartcloud_agent` role. This role has Composer's draft and dedicated taxonomy assignment/creation abilities without administrative publishing, broad native term management, or site-management capabilities. Configuration changes and draft operations are recorded in a redacted, tamper-evident audit chain.

Draft creation, human approval, and production release are separate control points. Composer does not expose content publishing, normal-content deletion, general-purpose media upload, plugin or theme changes, or user administration. It can search and assign existing Media Library images and, only when the active Site Contract explicitly enables it, ingest one bounded raster image from an exact administrator-approved HTTPS host. Normal WordPress publishing or optional Static Publisher and Static Site Guardian layers can handle the later release path.

Agent Canvas is an optional reference theme and starter environment for demonstrating Composer's complete contract model. It is not required and does not replace an agency's theme, patterns, or design process. Composer can instead use a contract built from capabilities discovered in an agency-built or compatible third-party block theme. Validation fails closed when a required template, pattern, block, or provider is unavailable.