# Agent Composer Structure Contracts

A Structure Contract turns a Blueprint's intended Gutenberg layout into a server-enforced document model. An agent addresses stable semantic IDs such as `hero.title` and declared extension slots instead of brittle array paths or unrestricted serialized markup.

The ownership model separates Blueprint-owned structure, instance-owned fields, and user-owned content inside controlled slots. Every slot declares allowed direct blocks, minimum and maximum children, and lock/appender behavior. Composer assigns stable identities to inserted trees and validates the entire document after every semantic insert, update, move, or removal. Invalid changes fail atomically.

Reusable governed structure lives in a published synchronized `wp_block` pattern. Posts keep native locked `core/block` references. Native Pattern Overrides carry declared instance fields, while Composer stores user-owned slot children on the individual pattern instance rather than the shared record. Editing one page therefore cannot alter every use of the synchronized pattern.

A Site Contract can make native WordPress Add New unmanaged, optionally Blueprint-driven, or required to initialize from a default Blueprint. Managed native documents receive the same patterns, contract, baseline, language, and server-side save protection as agent-created drafts without becoming agent-owned.

Compatible pattern revisions may change protected presentation while retaining required fields and slots. Breaking revisions enter an explicit invalid or reconciliation-required state. A versioned migration clones the active Config Set, registers successor contracts, previews exact source-to-target transformations, classifies automatic and review-required items, creates revision-bound proposals, and leaves accepted merges to a human. Migration never implies automatic bulk publication.

The theme owns templates, synchronized patterns, markup, styles, and `theme.json`; component providers own their schemas and materializers; Composer owns semantic contracts, governed mutation, reconciliation, proposals, and audit. AI Kit Knowledge Base sections may contain governed native Gutenberg or Agent Canvas descendants, while Feature and Doc Search retain their stricter child validation.
