Choose your interface
AAES Govern runs independently of AAES Operate. Its daemon API and language clients govern supported activity from your existing agents. Operator administration uses a separate authenticated console listener.
- HTTP API and authentication, with the Govern OpenAPI schema.
- Go, Python and TypeScript SDKs and the method and authorization matrix.
- CLI and offline verification. Local custody commands retain their own authority requirements.
- MCP transport and tested-client scope. The current bearer/stdio adapter does not support OAuth.
- Operator-console appearance, including its current limits.
Adding AAES Operate
The bundle keeps the two products' stores and permissions independent. Existing Operate history does not become governed evidence. Future execution requires explicit reviewed bindings; an unavailable Govern service cannot authorize fallback execution.
The shared workspace and new delegated developer interfaces are under implementation. Existing client authentication and endpoint contracts remain documented; do not send a token issued for one product or resource to another.
Read the Operate integration scope and prepare an evaluation.