An Xperience content item can feed a rendered website, a headless channel’s GraphQL response, other JSON integrations, and AI-assisted management workflows. Those consumers do not necessarily share the same release cadence, cache behavior, permissions, or tolerance for schema changes. A change that looks safe in the website preview can still break a mobile client, expose an internal field through an API, or give an agent incomplete context.
For teams operating this way, what should the cross-channel governance contract contain? I would expect each reusable content type and field to declare its intended consumers, owning team, workflow and approval requirements, draft-versus-published access, localization behavior, cache or freshness expectations, and compatibility policy. Automated checks could then compare required fields, linked-item resolution, URLs, embargo dates, and schema changes across the rendered page and machine-readable outputs before release.
Kentico’s current Management MCP is intended for local development, so I see it as a management surface in the change workflow rather than another production delivery endpoint. Should the governing policy live in the Xperience content model and channel configuration, in CI/CD, or in an external manifest that validates every consumer? How are teams preventing website-only or internal fields from leaking into GraphQL or JSON responses—or an agent’s context—while still maintaining one authoritative content source?