The Trinity of Abilities · Wicked Evolutions

Trinity / 01 — The three plugins

Three plugins. One operating layer for WordPress and AI.

Each one is a finished product that solves a specific problem on its own. Installed together they become the operating layer — the way your AI client and your WordPress site speak the same language without anything in between.

The Bridge · Node.js

Abilities MCP

Connect any AI client to any number of WordPress sites — from one place, on your machine.

Runs locally. Holds your keys in the OS keychain. Routes a single Claude or Cursor or Codex session across every site you operate. New site? One command. Multisite? Subsites included.

Open Abilities MCP

The Gate · WordPress Plugin

MCP Adapter

Turns your site into an AI-callable surface — with consent, scope, and safety baked in.

OAuth 2.1 with scoped keys, not pasted passwords. A consent screen the operator actually sees. Three-bucket redaction so secrets, payment data and contact PII never leak into chat. Every gate is named when it says no.

Open MCP Adapter

The Engine · WordPress Plugin

Abilities for AI

Every WordPress surface, named and reachable as a callable ability.

Content. Blocks. Themes. Plugins. Users. Filesystem. Cron. Multisite. The whole platform, registered as named operations the AI can discover, validate and run — never as raw database access. Growing every release.

Open Abilities for AI

Open source · GPL-2.0-or-later · Runs on your WordPress, your machine

Trinity / 02 — Who this is for

Built for the edge of WordPress.

The vibe-coder who builds with AI as co-pilot. The operator running a business across seven dashboards. The developer who wants to own the infrastructure layer. Three audiences. One stack. Different reasons to stop clicking and start talking.

Solopreneurs & entrepreneurs

The dashboard problem

You run your business on WordPress and you've been collecting dashboards — CRM, forms, store, support, courses, community. The Trinity makes those dashboards optional. The same operations are now reachable from a chat with the AI client you already use.

Agencies & WordPress developers

The fleet problem

You manage many client sites and the work is mostly the same work, repeated. The Trinity gives you one MCP connection across every client, with scoped keys per site and an audit trail per session. Multisite included.

Multi-brand operators

The portfolio problem

Several sites, several brands, one head. The Trinity lets you operate the whole portfolio through one conversation — without giving anyone outside your network a copy of your data. Your server. Your keys. Your memory.

Trinity / 03 — What's now possible

A WordPress site that can do, understand, and explain itself.

Most products in this space stop at the first floor. The Trinity opens three. Each tier composes on the one below it — and the third tier is the one nobody else is reaching.

01

Do things

CRUD · operations · workflows

Create a post. Update a setting. Assign a tag. Install a plugin. The named operations every WordPress operator already does — now reachable from the AI conversation, with the operator's role as the safety boundary. Most products stop here.

02

Understand state

Compiled diagnostics · cross-correlation

Site health, security posture, network overview, taxonomy health, theme audit — all compiled server-side, returned in one call. Eight sequential checks become one. The AI spends its intelligence on recommendations, not on figuring out what to ask for.

03

Understand meaning

Editorial intelligence · voice · arcs

Voice signatures per author. Opening patterns across every post. Series arcs. Headline statistics. Content depth distributions. WordPress goes from a content management system to a content intelligence system. Nobody else is building tier 3.

Trinity / 04 — The full sovereign suite

Pair the Trinity with Fluent. Run the whole business on open-source WordPress.

The Trinity makes WordPress AI-operable. Abilities for Fluent makes the suite of plugins you already pay for — CRM, forms, community, cart, support, booking, boards, affiliate — AI-operable too. Together: a full sovereign stack. No SaaS in the middle. No data leaving the site.

The equation

Trinity +
Abilities for Fluent +
WordPress core =
a full operating stack you own.

CRM Community Boards Forms Booking Support Cart Affiliate Snippets Messaging SMTP Auth

Conditional load · only what you run

What this means in your day

You ask your AI to look at last month's campaign, pull the contacts who replied, segment them by behaviour and queue tomorrow's follow-up. It does — through your plugins, on your site, with your role as the boundary.

Or: a support ticket arrives, the AI reads it, finds the customer's prior orders, drafts a reply, attaches the right knowledge-base article, and waits for you to say send.

The deep confirmation: every plugin you already chose, every workflow you already built, is now part of the AI-operable layer. You didn't bet on the wrong stack. You bet early.

Trinity / 05 — What it makes possible

Once the operating layer exists, memory becomes a WordPress feature.

The Knowledge Layer is not a fourth product. It's what becomes possible the moment the Trinity is in place — operational memory that lives inside your own WordPress, shared across every AI that ever connects.

Provider-agnostic

Claude on Monday. GPT on Wednesday. Gemini on Friday.

The observations live in your WordPress, not in any provider's context. The site remembers what every agent learned, regardless of who wrote the finding.

Operational, not archival

Not logging. Operational memory.

A log records what happened. Operational memory records what was learned — and the next session reads it before speaking. Compounding intelligence, on your server.