Current integration profile
Operate runs independently of Govern. The native Operate workspace uses corporate OIDC sign-in, current role and private-resource membership, and explicitly configured HTTP agent execution. New projects and tasks are private by default.
Installation and supported workload, directory and privacy integration guides ship with the evaluation package. A native endpoint, agent token or browser cookie is not a general AAES developer credential.
Choose an Operate interface
Each page describes its current status and product boundary. These are documentation entry points, not a claim that every interface is released.
Developer interfaces under implementation
A separately versioned product API, Go/Python/TypeScript clients, scoped CLI commands and Operate MCP tools are being implemented. They are not yet offered as a supported developer package. Package names and new endpoint prefixes are not installation instructions until a tested release supplies them.
These interfaces will share operation and permission semantics. They may request and observe protected human decisions; they will not turn those decisions into agent-completable approval flags. The Govern developer token and SDK are not an Operate client.
Operate appearance and the shared workspace are also under implementation. The existing appearance guide currently describes Govern.
Combined deployment
Adding Govern preserves native project, agent and task identifiers and operational history. Reviewed future execution gains Govern policy and evidence. Linking requires independent product-owner authority; discovery or purchase alone does not grant permissions.
Read the Govern developer contracts. Start a scoped evaluation to agree the exact versions, identity provider, execution profile and deployment acceptance.