The technical system behind WP Suite
Keep WordPress as the editing layer. Add governed content and client-owned runtime around it.
WP Suite separates presentation, governed AI drafting, modular product capabilities, and AWS runtime so each layer can evolve without turning the site into one opaque system.
Reference flow
Editors and site teams
↓
WordPress content + Agent Canvas visual system
↓
Agent Composer governed draft boundary
↓ human review
Gatey | AI-Kit | Flow | Static Publisher
↓
Client-owned AWS services and delivery
Agent Canvas is an independent native block theme, and Agent Composer is an optional draft-only governance layer. Add either one or both according to the site’s architecture.
Platform capabilities
Separate responsibilities before you combine products
The platform becomes easier to extend when presentation, content operations, product behavior, and runtime ownership stay visible.
Presentation stays native
Use Agent Canvas or map another compatible theme so editable templates, patterns, tokens, and accessibility rules remain the visual source of truth.
Draft automation stays governed
Agent Composer exposes approved page types, patterns, Media Library assets, fields, and relations to compatible agents, then stops at a validated draft for review.
Capabilities stay modular
Add Gatey, AI-Kit, Flow, or Static Publisher only where identity, AI, workflows, or static delivery solve a concrete requirement.
Runtime ownership stays explicit
Keep content in WordPress and place supported AWS services in the client’s account with clear boundaries for data, identity, operations, and billing.
Architecture layers
Four layers, each with a clear owner
01
WordPress content and editing
WordPress remains the CMS for authored content, Media Library assets, structured fields, relations, revisions, and human editorial review.
02
Visual system and site contract
Agent Canvas supplies a native block-theme foundation, while any compatible theme can expose stable templates, patterns, tokens, and presentation rules.
03
Governed operations and products
Agent Composer controls allowed draft paths. Gatey, AI-Kit, Flow, and Static Publisher provide focused capabilities without owning the whole site.
04
Client-owned AWS runtime
Cognito, API Gateway, Lambda, Bedrock, S3, CloudFront, and related services can run in the client’s account when the selected use case needs them.
Adoption path
Build the contract first, then add runtime
Start with the existing WordPress site and introduce only the layers that create a concrete operational benefit.
- Establish the visual foundation — Adopt Agent Canvas or document an existing compatible theme, its templates, patterns, tokens, and supported content model.
- Define governed content paths — Configure Agent Composer with the approved page types, pattern sequences, media placement, fields, relations, and draft-only review boundary.
- Add focused capabilities — Introduce identity, AI, forms, workflows, or static delivery through the relevant WP Suite products rather than a single all-purpose integration.
- Deploy, review, and operate — Provision only the required AWS components, confirm ownership and observability, and keep publication plus production changes under human control.
Choose the next layer
Use the platform as a map, not a mandatory bundle.
Start with a visual system, governed content operations, one product capability, or a client-owned deployment path. Add the next layer only when the project supports it.