Resources for governed WordPress agents
Find the answer.
Keep the boundary clear.
Learn the control model, build one safe workflow, and resolve operational questions without losing sight of identity, authority, policy, evidence, or recovery.
Start with the path
From installation to one safe Ability.
The quickest way to understand governance is to follow one real request through the complete control path.
Install
Activate RuleFence and confirm the local control plane is ready.
Register
Register the agent so every request has a named operational identity.
Grant
Grant one narrow WordPress Ability with an explicit policy decision.
Inspect
Inspect the outcome, evidence, and recovery path before expanding access.
Resource library
Choose the depth your question needs.
Start broad when learning the model. Go directly to focused guidance when a real workflow is waiting.
Documentation
Understand the control model
Identity, Abilities, policy, approval, evidence, recovery, and the WordPress authority ceiling.
Open documentationGetting started
Build your first safe path
Install the plugin, register one agent, grant one Ability, and inspect the first decision.
Open getting startedDeveloper guide
Integrate without hidden authority
Register capabilities, shape request context, and return evidence in a predictable contract.
Open developer guideKnowledge base
Resolve a specific question
Short operational answers for setup, permissions, approvals, evidence, and recovery.
Open knowledge baseSupport
Get help with a real workflow
Bring the site, agent, Ability, decision, and evidence together so support can start with context.
Open supportAnswers at the decision point
Search by what happened—not by product vocabulary.
Operational questions rarely arrive as feature names. Start with the request, the decision, or the outcome and trace the relevant guidance from there.
- Why was this request blocked?
- Which authority allowed this action?
- Where is approval required?
- What evidence should remain?
Guides by responsibility
The same boundary, explained for your role.
Each guide begins from the responsibility you carry while preserving the same non-negotiable control model.
Know what agents can do on your site.
Read identity, permissions, approvals, and evidence in operational language.
Explore site-owner guidanceRegister capability without inventing authority.
Build against explicit WordPress Abilities, context, decisions, and evidence.
Open the developer guideCarry standards across sites responsibly.
Reuse governance patterns while keeping every site boundary distinct.
Explore agency guidanceWhen guidance is not enough
Use the support path that matches the issue.
Good support begins with the right context. Include the site, agent, Ability, decision, and evidence when they are available.
Common resource questions
Begin in the right place.
You should not need to read everything before taking one safe next step.
I am new to RuleFence. Where do I begin?+
Start with Getting Started. It follows one agent and one safe Ability from installation through the first inspectable decision.
Where can I understand a specific concept?+
Use Documentation for the complete model: identity, native authority, policy, approval, evidence, recovery, and emergency control.
Where should developers start?+
The Developer Guide focuses on capability registration, request context, policy decisions, outcomes, and evidence contracts.
What should I include in a support request?+
Include the WordPress site, managed agent, requested Ability, policy decision, outcome, and relevant evidence whenever possible.
Start with one explicit boundary
Give one agent one safe Ability.
Learn from the complete path.
Install locally. Keep WordPress in control. Expand only when the evidence supports it.