System
Connection, environment, integration health, one operation’s schema on demand, and the ledger of everything that has changed. This is how a session starts well instead of failing halfway through.
Everyone. The first two operations of a session are the difference between a plan that works and a plan built on assumptions.
Each of these is carried by named operations that exist in the release you can download today. The ids under every answer are the calls involved — nothing here is a plan.
Connection first, then integrations. Two calls tell an agent which modules are live and which plugins are present before it proposes anything.
SiteHelm
system-connection needs read system-integrations needs manage_options The same ledger the plugin’s Activity screen shows: what changed, when, by whom, and what can still be rolled back.
audit-list needs manage_options One named operation’s full input and output schema, fetched on demand, so an agent loads the schema it needs rather than all of them.
system-operation-schema needs read system-environment needs manage_options Connection, environment, integration health, one operation’s schema on demand, and the change ledger.
Nothing extra to install. This module runs on core WordPress alone.
5 operations that only report. A read still asks WordPress for a capability against the object.
0 that change something — each one previewed as a diff, snapshotted, verified by reading the site back, and reversible from wp-admin.
Free, permanently. Nothing in this area moves into a paid tier later.
The ledger is a record, not a control. Pausing writes, revoking an application and switching operations off all live in wp-admin, out of reach of any agent.
Start every session with system-connection, then system-integrations. Two calls tell an agent what is actually available before it plans anything.
system-operation-schema returns one named operation’s full input and output schema, so an agent fetches the schema it is about to use instead of loading all of them.
audit-list is the same ledger the plugin’s Activity screen shows: what changed, when, by whom, and what can still be rolled back.
Get the free plugin How a write is guarded
Site-wide settings, schema, the 404 log and redirections, and bulk fixes across up to fifty posts in one previewed, reversible change.
8 opsEvery area of the catalogue, by what it lets you do.
indexEvery operation on the site in one list, with capability, risk and rollback.
reference