Capability ownership
Sandbox adapters declare resource/network capabilities. Harnesses declare conversation, Tools, and initialization. Tool adapters participate in approval capability. One layer cannot grant another layer’s capability. Required capabilities express conditions, not feature switches. A buildable OCI recipe still fails compatibility when the Provider lacksoci_image. A verified model endpoint does not prove all Harness tool-calling and continuation behavior.
Read an evidence row
Check Provider, Harness version/image digest, model endpoint/protocol, SDK, task scope, date, and cleanup. Separate passed, failed, unrun, and explicitly unsupported outcomes. Keep unknown outcomes unknown. Historical results prove their recorded executions. Current preflight keeps verification unverified instead of automatically certifying new configuration from old successes. Account, endpoint, or deployment changes may require fresh evidence.Two decisions in practice
Example one: a buildable image with an unsupported combination. Building an OCI Harness image locally establishes that the build produced an image. If the selected Sandbox adapter lacksoci_image, Session preflight rejects it with sandbox_oci_image_unsupported. A private image additionally requires private_oci_image and a usable registry Secret. Adding required_capabilities cannot supply those capabilities. Choose a suitable execution path, preflight again, and verify actual image pull, startup and work. Do not record build success as a cloud pass. This illustrates the mechanism rather than permanently assigning a support status to a particular Provider.
Example two: a verified model connection without a verified Tool journey. An endpoint check does not establish that the selected Harness can complete tool calling through that protocol. Check the Harness model protocol and tools declaration, then the bound Tool’s operations, authorization and approval capabilities. The real journey must observe the model issuing a call, Runtime / broker handling it, required authorization or approval, the result returning to the model, and the same Run continuing to completion. Receiving model text alone proves none of that chain. Record protocol incompatibility, execution failure and unexecuted tests separately.
Supported and unverified can both be true
Combination resolution separates structural judgment from real execution. This excerpt illustrates field relationships; it is not a captured preflight response:ready: true does not reserve cloud quota, pull the image or execute the model and every Tool. An incompatible request can receive an error response instead of this JSON; do not assume rejection reasons always arrive inside a successful response.
Choose evidence for your application
- List required behavior. Examples include project upload, multi-turn edits, approved writes, private previews, idle wake and post-close downloads. Preserve the application journey rather than dropping requirements missing from existing tests.
- Pin the combination. Record control-plane revision, SDK version, Sandbox connection, Harness version / digest, model endpoint / model ID / protocol and Tool configuration. A connection display name does not uniquely identify a test.
- Eliminate known structural conflicts. Use catalog, connection validation and preflight for their respective questions. Resolve explicit unsupported combinations rather than repeatedly submitting tasks as a compatibility repair.
- Find matching prior evidence. Check steps and dates in verified combinations. A newer focused result updates only the combinations it covers; it does not erase previous failures or unresolved operations.
- Test missing critical branches. Run the required SDK journeys independently and record outcomes and cleanup. Disconnects, authorization, approval and recovery need their own assertions; one successful answer does not replace the full journey.
Why capability names cannot be combined indiscriminately
The resolver builds a capability set with explicit ownership rules. It does not union every string returned by every adapter.
These are resolver rules, not proof that an approved operation was executed correctly. The specific Tool’s policy and actual call still determine whether approval is required. Catalog data is discovered through the Harness registry; connection adapters and the combination resolver establish the corresponding boundaries.