Verify the control plane after activation

Read the readiness score

Readiness is an explainable 100-point score for the whole site or for one agent. It covers compatibility, connection health, permissions, approvals, sessions, audit state, and integration.

Every deduction names what is missing and links to the screen that fixes it. A low score on a fresh install is normal and expected — you have not granted anything yet.

Run runtime verification

Runtime verification re-tests the governance controls on the installed site. It exercises the real behaviour rather than asserting it: that default deny refuses, that a native denial cannot be overridden, that an approval cannot be replayed, that the audit chain verifies, and that emergency mode actually stops a request.

The emergency check pins the mode in memory rather than switching your site, and asserts the stored mode is unchanged when it finishes. Verification must never block real agents to prove a point.

Reading the results

An empty Ability registry is not a failure. A fresh site with no registered Abilities has nothing to govern, and verification says so rather than reporting the install as broken.

When to re-run it

• After any plugin update.
• After a WordPress or PHP upgrade.
• After a host migration or a database restore.
• Before granting an Ability classified as high or critical risk.

Related guides

• SetupUpdate safely, and what never changes

  How schema upgrades run, what a release will never do quietly to your permissions or evidence, and what to check after updating.

• EvidenceVerify the audit chain

  HMAC-SHA-256 chaining with a signed head means the record can prove it has not been edited. How to run a full-chain verification and when it is worth doing.

• AuthorityGrant your first permission

  Pick one narrow, reversible, non-public Ability, set it to allow, run one real request, and read the decision it produced before granting anything else.