GATE 01
Define the state change
Name the exact record, fields, preconditions, and terminal state. Avoid labels such as “integration” that hide the operation.
Workflow qualification guide
Documents and notes
Attach documents, route notes, and verify chart placement. This guide frames the questions that determine whether the safest practical path is a vendor interface, an approved integration partner, or a controlled UI workflow.
GATE 02
Test the supported interface
Check the vendor method, required scopes, customer enablement, rate limits, and the environment where the operation will run.
GATE 03
Design verification
Read the resulting system-of-record state independently. A click, request, or success toast is not sufficient evidence.
GATE 04
Qualify a controlled UI path
Only if the supported interface is impractical: constrain inputs, approvals, exception handling, and stop conditions before execution.
Decision rule
Prefer a practical API. Prove the last mile.
If no practical supported interface can complete this operation, OpenAdapt can turn a demonstrated UI task into an approved program, verify the resulting state, and halt on ambiguity.
Qualify this workflow