A successful model response is only part of an operator test. The proposed plan must name supported capabilities and supply valid parameters. The execution path must apply the correct customer context and policy. The connector must handle the result without inventing certainty.
Test the boundaries
Include malformed plans, unsupported capabilities, missing permissions, duplicate events, concurrent attempts, unavailable sources, and ambiguous downstream outcomes. These cases reveal what the system does when the normal path cannot complete.
Use clearly identified fixtures or permitted source recordings. Test data must remain separate from real-data tenants. Expected results should describe both the action decision and the record left for review.
Validate the environment
A local test does not establish that the same capability is deployed, enabled, or available to a particular user. Review the deployment’s actual inventory, source credentials, runtime switches, and operating limits.
The public documentation describes a reference development model. It does not provide a public SDK or a production promotion path. Managed deployment review confirms the tools and environments available for the project.