AYSA Execution
Approved Execution
Approved execution is the controlled attempt to apply a specific proposal after its authorized reviewer has accepted the exact target and payload.
What it means
Approval makes the item eligible for execution but does not prove it ran. The workflow must still confirm connector capability, current state, dependencies and destination response before verification.
Why it matters
The distinction keeps approved, applied and verified evidence separate, preventing dashboards from reporting progress that exists only as an accepted recommendation.
Example
An editor approves a replacement title for post 3441; AYSA checks that the current title is unchanged, updates that post and then verifies the rendered title value.
Common mistakes
Do not label a proposal executed immediately after approval, broaden one approval to unrelated URLs, skip fresh authorization checks or close the issue before observing the destination.
How AYSA handles this
Signals reviewed
approval record, approved payload hash, current target value, connector response, rendered result
Problem AYSA can identify
AYSA can pause an authorized WordPress item when its approval is missing, stale, out of scope or inconsistent with the current object.
Recommendation prepared
The execution record binds the reviewer, proposal, target, prior value, allowed operation and success condition.
Approval preview
Before the decision, AYSA exposes the exact WordPress object and field rather than a broad instruction such as improve this page.
Execution
AYSA can attempt the bounded accepted update using the active connected capability and records the result separately from approval.
Verification
The destination is read again so a successful request, saved value and rendered result can be distinguished.
Limits
An approval cannot authorize unavailable capabilities, unrelated changes, autonomous spending or guaranteed ranking improvement.
Sources and further reading
- WordPress REST API Handbook — Posts — Official platform documentation
- WordPress REST API Handbook — Post Revisions — Official platform documentation
- WordPress REST API Handbook — Authentication — Official platform documentation
- WordPress Plugin Handbook — Roles and Capabilities — Official platform documentation
- OWASP Cheat Sheet — Authorization — Primary security guidance
Written by Marius Dosinescu. Reviewed by AYSA SEO Editorial Team · 2026-07-28 00:00:00.
Quick answers
Frequently asked questions
Does approved execution mean the website was already changed?
No. It means a bounded proposal is authorized to attempt execution; applied and verified are later evidence states.
Can an approval remain valid after the page changes?
Not automatically. A material change can invalidate the reviewed context, requiring the item to pause and return for review.
SEO execution campaign
Less SEO work. More organic growth.
AYSA monitors your website, finds opportunities, prepares the work, asks for approval and executes accepted changes so you can grow without living in SEO tools.
