Deployment readiness

Integrate with the ready deployment already connected to your workspace. The returned connection bundle and capability state define the supported customer boundary.

Before routing traffic#

1. Confirm the intended workspace and deployment are available.
2. Use the supplied base URL and a valid platform key.
3. Keep the configured customer provider, credential, protocol, and model aligned.
4. Persist task and operation identity, set explicit output limits, and disable automatic retries.
5. Verify hold handling, operation recovery, and executor controls in your application.

The current connection can require use of an existing deployment. It does not provide general self-service enrollment by creating another project.

Operational ownership#

Your application owns task orchestration, tool execution, resource permissions, and effect reconciliation. Integrity supplies the connected review service and its session controls. SDKs do not configure internal containers, model artifacts, or runtime credentials.

A process health check is not deployment acceptance. Verify the actual connection and inspect Runs for your own request outcomes.

Handle changes and incidents#

Track the deployed connection and session revisions during key changes, configuration updates, and incidents. Use explicit authorized controls for unresolved sessions; do not bypass a hold by changing providers or generating replacement IDs.

Read Security and evidence, Errors and recovery, and Versioning and support.