Evidence
Read the request evidence
Evidence preserves the full request context: identity → Ability → decision → outcome. Read it in that order.
- Activity & evidence
- 3 min read
The shape of a record
- Identity
- The managed agent, its environment, and the connection it authenticated with.
- Ability
- The exact registered name, plus its classification at the time of the request.
- Context
- The redacted input preview and the target the action would affect.
- Decision
- Which gate answered, what it decided, and why.
- Outcome
- What actually happened, and what changed in WordPress.
Reading it in order
Work top to bottom and stop as soon as the record answers your question. Most investigations end at decision — the gate is named, and the fix follows from which gate it was.
Only continue to outcome when the request actually executed and you need to know what it touched. That is the section recovery works from.
Linked, not duplicated
Evidence is linked to the decision rather than copied into it. An outcome points at the objects affected, so recovery can act on exactly those and nothing else. It is not a text log you have to parse.
The decision is recorded before the agent gets its response. There is no window in which an action has happened and the record has not caught up.
Activity & evidence
Keep the boundary while you fix the problem.
A good fix restores intended behaviour without creating a second path around WordPress or the governed request lifecycle.