Automation is a chain of decisions. The interface is only its most visible link. A useful review starts with the inputs, follows every rule, and ends with the controls available when conditions change.
INPUT→RULE→ACTION→EXIT
Can you explain the trigger?
If a platform cannot state what causes an action, the user cannot distinguish disciplined automation from opaque discretion. We look for explicit thresholds, schedules and data dependencies.
Who controls the exit?
Withdrawal delays, account transfers and revoked API permissions matter more during stress than during onboarding. The scorecard treats exit friction as a first-class risk.