PRODUCT
The governed execution layer for WordPress.
GES gives AI agents a controlled way to inspect, propose and execute real WordPress operations—without turning every prompt into unrestricted site access.
INTENT
↓
GES CONTROL PLANE
Permission
Live state
Native preview
Human review
Exact confirmation
Apply
Read-back verification
Audit
↓
WORDPRESS STATE
INSIDE GES
Not a wrapper around WordPress. A governed runtime for agent actions.
GES separates what an agent wants from what WordPress is actually allowed to do. Every layer exists to reduce ambiguity before a write and increase evidence after it.
01
Connection & authority
Identity, connection permissions and native WordPress capability checks define the boundary before work begins.
02
Native adapters
Supported WordPress resources are read, previewed and mutated through explicit adapters rather than generic blind writes.
03
Reviewed Jobs
Meaningful changes become inspectable jobs with exact proposals, human review and action-specific confirmations.
04
Verification & evidence
GES reads native state back after execution, records evidence and routes uncertain outcomes into reconciliation instead of blind retry.
TRANSACTION MODEL
Every meaningful write becomes an inspectable transaction.
The agent supplies intent. GES turns that intent into a bounded sequence with explicit state, review and evidence around the actual WordPress mutation.
01 / RECEIVE
Intent enters the system.
A request is interpreted against the connected site's permissions and the exact resource being targeted.
02 / CAPTURE
Current state is recorded.
GES reads the live WordPress state before proposing a mutation, giving the review a concrete baseline.
03 / PROPOSE
The exact change is generated.
A native preview defines what will change rather than relying on a vague description of intent.
04 / AUTHORIZE
Approval binds to the reviewed action.
The reviewed mutation receives the specific confirmation required to proceed.
05 / EXECUTE
WordPress performs the guarded mutation.
GES applies through the supported native adapter while the live-state and permission gates remain in force.
06 / RECONCILE
Outcome is verified, not assumed.
The resulting state is read back. If execution is uncertain, the system reconciles reality before another write is considered.
NATIVE BY DESIGN
WordPress stays the source of truth.
GES is designed around the state WordPress actually holds. Where a resource is supported, the system reads native state before execution and verifies native state again afterward.
Real Gutenberg structure
Supported content and layout operations work with native WordPress block structure so the result remains editable in WordPress.
Real WordPress authority
Connection permissions and WordPress capability checks remain part of the execution boundary rather than being replaced by agent intent.
Real state after Apply
Verification reads the resulting resource back from WordPress. A request being sent is not treated as proof that the intended state exists.
START HERE
Connect one WordPress site. Give your agent a governed execution path.
Start with a bounded connection, keep human review where it matters, and let GES turn agent intent into verified WordPress state.