CONSONANTVIEW THE PLAN ↘

WORDPRESS 7.1 / ARCHITECTURE BRIEF

WordPress is building the machinery. Consonant moves up a layer.

A practical roadmap for turning native WordPress Abilities into a safer, discoverable, design-aware orchestration system.

EXPLORE THE ROADMAP↘SEE WHAT SHIPPED ↗
LIVE EVIDENCE

WordPress 7.1 is already exposing Core Abilities on an active install.

core/get-site-infoREADONLY
core/get-user-infoAUTHENTICATED
core/get-environment-infoREADONLY

01 / THE ARCHITECTURE

Stop handcrafting the bridge. Use the registry.

Consonant should discover capabilities from WordPress, reason over their schemas, and execute them through a focused transport—not pour hundreds of individual tools into the agent context.

01

Discover

find_wordpress_abilitiesQuery the native registry instead of assuming what a site can do.
02

Interpret

inspect schema + annotationsRead typed inputs, outputs, permissions, and machine-readable risk metadata.
03

Execute

execute_wordpress_abilityInvoke the right capability through one scalable transport layer.
04

Verify

backup → run → validatePreserve Consonant’s checkpoints, hashes, audit trail, and rollback discipline.

02 / THE SLEEPER FEATURE

A native place for the safety kernel.

WordPress 7.1’s execution lifecycle gives Consonant one central point to classify risk, enforce permissions, create a checkpoint, and verify the result.

readonly: truedestructive: falseidempotent: true
AI REQUESTExecute Ability
CLASSIFYRead or write?
READ → RUNWRITE ↓
  1. 01

    Create backup checkpoint current state

  2. 02

    Record intent permission + audit entry

  3. 03

    Execute normalized typed input

  4. 04

    Validate result hash + expected outcome

ENGINEERED SHELLSTRUCTURE LOCKED
<section class="cal-system">
  <div class="technical-lines" />
  <div class="copy">
    [ EDITABLE HEADING ]
    [ EDITABLE PARAGRAPH ]
  </div>
  <div class="image-frame">…</div>
</section>
+

Safe Gutenberg content lives inside a protected Consonant composition.

03 / EDITOR OPPORTUNITY

Engineered shells. Safe editable zones.

Let a client change a heading, paragraph, or CTA without exposing layout, geometry, animation, CSS, or JavaScript. Prototype the serialization first; don’t migrate production sections until Gutenberg proves it will preserve them.

EDITABLECopy · headings · CTA text
PROTECTEDStructure · classes · motion · design

04 / DELIVERY SEQUENCE

A focused roadmap, not a rewrite.

Adopt the standard progressively. Keep the current REST layer as a proven fallback while the new architecture earns trust.

010.4

NEXT MEANINGFUL RELEASE

Abilities-aware core

  • ↳Native Ability discovery and execution
  • ↳Selected Consonant operations registered as Abilities
  • ↳Schemas derived from WordPress JSON Schema
  • ↳Lifecycle logging, permissions, backups, and annotations
  • ↳WordPress 7.1 iframe-editor compatibility audit
  • ↳Current REST routes retained as a compatibility layer
020.4.x

EDITOR IMPROVEMENTS

Safer editing surfaces

  • ↳Prototype Editable Zones inside Custom HTML
  • ↳Inspect and support native responsive styles
  • ↳Add WordPress 7.1 serialization regression tests
  • ↳Test Code Preview in the fully iframed editor
03LATER

WHEN THE ECOSYSTEM STABILIZES

A shared knowledge layer

  • ↳Guidelines and Knowledge integration
  • ↳More operations migrated from bespoke REST contracts
  • ↳Automatic third-party plugin capability discovery
  • ↳WordPress as registry; Consonant as orchestration and safety

THE POSITION / WHY CONSONANT STILL MATTERS

WordPress can tell an agent what functions exist. Consonant determines which one should be used, how to use it safely, what must not be touched,and whether the result is actually correct.
OPEN WORKSPACE↗