Operations
Limits and FAQ
Check the current protocol, review, and version-management boundaries.
Use the deployment capability report and supported protocol contract when deciding what your integration can do.
Current Base capabilities#
| Capability | Current boundary |
|---|---|
| Action and final-output review | Supported before release for admitted requests. |
| Initial compiled input contract | Verified before customer inference in Enforce; a held or unavailable contract stops the request. |
| Per-request input rewriting / tool-result quarantine | Unavailable before customer inference. |
| External executor authorization and reports | Supported for configured actions; execution and effect reconciliation remain with your harness. |
| Signed receipts | Require an already registered signer for the exact connection, scope, and tool. |
| Prepared Case review / dynamic executor registration | Unavailable on this connection. |
| Customer-version prepare / train / activate / rollback | Unavailable on this connection. |
| Task completion | Closes the platform session; no remote-close operation. |
| Native billed tokens and derived cost | Unknown, not zero. Separately named prepared-input and returned-output observations may be available; they are not billed tokens or physical GPU time. |
Does provider compatibility cover every feature?#
No. The current adapter supports explicit text/history and supported tool proposals in Chat Completions, Responses, and Messages. Remote Responses history, background requests, opaque references, media evidence, multiple choices, server-executed tools, and legacy function-call syntax are unsupported. Read Model connection.
Does release prove the task is safe or complete?#
No. Judgment can be incomplete or wrong. Integrity can assess only available evidence; it cannot reveal hidden model reasoning. A released proposal is not proof that an action executed or the task succeeded. Keep resource permissions, sandboxing, and artifact validation in your application.
Can I create another connected deployment?#
The current connection can require the workspace's existing deployment. Follow the setup availability state. An SDK option, generic project, or legacy key does not enroll another connection.
Can I retry a held or interrupted request?#
Do not retry automatically. Recover the original operation and reconcile the outcome. New IDs can create new work without resolving the first operation. See Errors and recovery.
What happened to standalone checks?#
Standalone classifier checks are retired. The historical check service returns HTTP 410 with standalone_checks_retired; the current model gateway does not expose those routes and returns HTTP 404 for them. Historical URLs and records remain available for migration and interpretation. New integrations use an enabled deployment and the session contract.