Get started with RuleFence

One agent. One Ability.
One complete path.

Begin with a request small enough to understand completely. Make the acting identity explicit, preserve WordPress authority, and verify the result.

Start the setup path Open documentation

Use a site you manage Begin low consequence Default deny stays active

First governed request Setup path ready

YOUR FIRST CONTROL PATH

From activation to readable evidence.

Keep the scope narrow until every decision is understandable.

01Install the pluginControl plane available

02Create identityAgent and purpose named

03Register one AbilityNative authority preserved

04Choose a decisionAllow, review, or block

05Run and inspectDecision and outcome recorded

Unknown authority remains blockedInstall → Identify → Register → Decide → Verify

Choose the first boundary

Begin where a mistake is easy to understand.

The first request should teach you how governance behaves—not test how much consequence the system can absorb.

Use a controlled site

Work on a site you manage. Prefer staging when it is available.

Choose reversible work

Start with a result you can check and safely undo if necessary.

Keep consequence low

Avoid destructive changes and sensitive access during the first path.

Install and open

Put the control plane inside WordPress.

Installation creates the place where authority is governed. It does not grant an agent permission by itself.

Download

Get the plugin ZIP from the Download page.

Upload

Open Plugins → Add Plugin → Upload Plugin.

Activate

Activate RuleFence and open its control plane.

Confirm

Confirm the control plane loads before authorizing an agent.

Download RuleFence

Step one · Managed identity

Name who is acting before judging the action.

Create one identity that describes the agent, its purpose, and its environment. Do not reuse one identity for unrelated agents.

Use a clear agent name
State the operating purpose
Identify the environment
Keep ownership understandable

Managed identity Draft

CAAGENT NAMEContent Assistant

Helps prepare and inspect content changes.

PURPOSEContent workflowENVIRONMENTStaging

Identity describes the actor. It does not create authority.

Registered Ability Native

WORDPRESS ABILITYcore/get-site-infoRegistered

Native permissionMust pass

ScopeRead only

Unknown requestsBlocked

Step two · Native authority

Register one Ability. Never invent permission.

Select one WordPress Ability the site already recognizes. RuleFence can narrow or review authority, but it cannot silently expand it.

Choose one exact capability
Confirm the WordPress user can perform it
Leave unrelated requests unregistered

Read the authority model

Step three · Policy decision

Choose the smallest decision that fits.

WordPress authority answers “can.” Policy decides whether this exact request may proceed now.

LOW CONSEQUENCE

Allow

Proceed when identity, authority, scope, and policy all pass.

For narrow, understood work

JUDGMENT REQUIRED

Require approval

Pause when a person should review the exact action first.

When consequence needs context

OUTSIDE THE BOUNDARY

Block

Stop requests that lack authority or exceed the intended scope.

Default for unknown access

Step four · Run one request

Follow the request—not just the final status.

Submit one low-consequence request and inspect every gate. A successful result matters only when you can explain why it was allowed and what WordPress did.

Managed identity matched
Native authority passed
Policy returned a decision
Outcome was recorded

Governed request Completed

CAREQUESTRead site health

01IdentifyContent Assistant

02AuthorizeNative permission passed

03DecideAllowed by policy

04ExecuteRead completed

Step five · Evidence

Confirm the decision and the actual outcome.

A policy decision is not proof of execution. Keep both sides of the event readable.

DECISION EVIDENCE

Why the request proceeded

Identity matched · Authority passed · Policy allowed

OUTCOME EVIDENCE

What WordPress actually did

Ability executed · Result recorded · No broader access used

After the first request

Expand one dimension at a time.

Keep the successful path as your reference. Change the agent, Ability, policy, or environment separately so the effect stays visible.

Understand the modelIdentity, authority, policy, evidence, and recovery.Choose the next workflowApply the boundary to a real operating need.Get help with a stopped pathBring the request, decision, and outcome context.

Setup questions

Keep the first path understandable.

If setup becomes difficult to explain, reduce scope before granting more access.

Does activation give an agent permission?+

No. Activation installs the control plane. The agent still needs identity, valid WordPress authority, a registered Ability, and a passing policy decision.

Which Ability should I test first?+

Choose a narrow, low-consequence, reversible action on a site you control.

What if native authorization fails?+

Do not bypass it in policy. Check the WordPress user, role, capability, and Ability registration.

What should I save when asking for help?+

Keep the identity, requested Ability, policy decision, and recorded outcome together.

Begin with one complete path

Make the first request
small enough to explain.

One agent. One Ability. One decision and one recorded outcome.

Download Free Open documentation

One agent. One Ability.One complete path.