Retrieval and usability, control 18 of 18
R-18 Make agent-assisted transactions explicit and reversible where possible
P0Hard gateNeeds your evidence
An agent-friendly interface must still preserve user authorisation, correct terms and transaction safety. Discovery optimisation does not authorise an agent to purchase or submit data.
- Priority
- Gate. A FAIL stops publish or launch.
- Hard gate
- Yes. A FAIL stops publication, whatever the score.
- Change class
- APPROVAL_REQUIRED: Required exact authority must be valid before the consequential action.
- Quality bucket
- Not scored: hard gate only
Evidence to review
- End-to-end task trace, duplicate-action tests and verified confirmation behaviour.
How to implement
- Expose current totals, important terms and a review step before commitment.
- Separate quote, basket and final-submit actions.
- Prevent accidental duplicate submissions and surface success or failure clearly.
- Test ordinary human and permitted agent flows in a non-production environment.
How UltimateSEO checks this
Needs your evidence. No automated check covers this control, so it stays UNKNOWN until evidence is supplied.
States used: PASS, FAIL, UNKNOWN, NOT_APPLICABLE or BLOCKED. UNKNOWN is never shown as a pass. How states work.
Part of The UltimateSEO Framework v4.3, catalogue dated 2026-10-14. Evidence states, control states and the publish gate are explained on the hub.