<div class="wp-block-smartcloud-ai-kit-feature"></div>
Sign In

SmartCloud Agent Composer Overview

SmartCloud Agent Composer is the WordPress plugin layer of a governed, agent-assisted content production solution. It combines an explicitly activated configuration with the active theme's discovered or declared design capabilities, then exposes a restricted set of operations for creating and updating validated Gutenberg drafts.

Composer is not a general-purpose WordPress administrator and it is not a theme. It owns configuration, validation, audit, draft ownership, and execution safety. The active theme owns presentation: templates, patterns, theme.json settings, style presets, and the final frontend rendering.

The operating model​

Composer joins four kinds of information:

  1. A Config Set identifies one versioned configuration package and its lifecycle state.
  2. A Site Contract describes site-wide editorial, structural, and design rules.
  3. Blueprints define the allowed target, template, patterns, blocks, sequence, excerpt policy, and constraints for each page type.
  4. Theme and provider discovery confirms what the current WordPress installation can actually render or execute.

Only one validated Config Set is active on a site. Editing happens in a separate working copy; imported packages also remain inactive until an administrator reviews, validates, and activates them.

What an agent can do​

After an authenticated client connects through the WordPress MCP Adapter, Composer can expose abilities that:

  • load the selected page blueprint and current design context,
  • list approved patterns and registered blocks,
  • validate a proposed section plan without saving it,
  • create an agent-owned draft,
  • update only a draft assigned to the current agent,
  • inspect a draft and obtain a fresh preview,
  • search existing Media Library images and materialize valid Image blocks,
  • delegate a component operation to an installed provider that owns the corresponding WordPress Ability.

Composer does not expose content publishing, normal-content deletion, media upload, theme or plugin modification, or user administration. Preview is a real short-lived WordPress draft, and expired preview drafts are removed only after Composer verifies their private ownership markers.

Why the theme matters​

A contract can refer only to capabilities that exist on the current site. Composer therefore discovers templates, registered patterns, registered blocks, theme.json settings, and an optional theme manifest. Validation fails closed when a required template, pattern, block, or provider is missing.

This model supports two useful configurations:

  • Canvas or another contract-aware block theme can provide a complete, intentionally mapped visual system.
  • Any compatible third-party block theme can provide a partial capability set. An administrator creates a smaller contract using only the templates, patterns, blocks, and presets that discovery confirms.

Changing the theme never silently imports or activates a new Config Set.

Safety and accountability​

Every content write checks the full block tree, target post type, template, ownership, agent capability, and optimistic-concurrency token. Audit events are redacted and stored in a tamper-evident SHA-256 hash chain. Configuration changes use explicit Apply or Discard controls, and activation is bound to a fresh validation receipt for the exact site and checksum.

The dedicated smartcloud_agent role is the recommended execution identity. It has Composer's draft capability without receiving publishing, deletion, plugin-management, theme-management, media-upload, or unfiltered-HTML privileges.