Governed CLI + MCP

Cloud and Kubernetes operations · hybrid deployment

Hybrid operations architecture and trust boundaries Existing AI clients call a local MCP adapter. Humans use a deterministic CLI. Both use the central operations API. Policy and separately verified human approval gate isolated execution against Kubernetes and cloud APIs, or reviewed GitOps proposals. Sanitized evidence returns to clients; durable audit spans decisions and outcomes. Select a component for details. ENGINEER WORKSTATION · NO INFRASTRUCTURE CREDENTIALS EXTERNAL MODEL PROVIDER CENTRAL CONTROL PLANE · COMPANY IDENTITY + ENFORCEMENT ENVIRONMENT TRUST ZONES · SCOPED WORKLOAD IDENTITIES stdio provider connection typed HTTPS requests authorized jobwrites: approved plan sanitized evidence → host → provider Every read and write is authorized. The model cannot approve an operation. Existing AI clientClaude Code / Codex CLI Local MCP adapterneossh mcp serve · stdio Model providerExisting client subscription Deterministic CLIHuman commands · same API Operations APICompany SSO · typed requests Policy + plan storeDeny by default · live checks Change proposalsGitOps / IaC · no direct apply Isolated executionTyped jobs · scoped workers Human approvalSSO + user presence · digest Audit + filtered evidenceDurable intent, result, verification Kubernetes APIScoped RBAC + admission Cloud APIsAccount / project scoped IAM Review + deploymentProtected PR → CI → controller