Skip to content

ADR-0002: Customer-Resident AWS-First Deployment

Target architecture — not the current operating contract

Packaged AWS deployment is not included. Use Source deployment for the implemented distribution.

Status

Accepted — 2026-08-19

Context

Mission Control governs sensitive enterprise identities, provider and MCP access, policy, approvals, operating telemetry, selective content, evidence, and business Outcomes. Customers need this control plane to align with their network, SSO, secret management, residency, retention, security, and operating controls. Attempting equal operational support across every cloud, SaaS tenancy, and on-premise pattern in the first release would dilute the reference architecture and delay validation of the product contracts.

At the same time, tying product semantics to one cloud's proprietary identity, integration, observability, or evidence interfaces would undermine provider and deployment portability.

Decision

The first reference deployment is single-tenant inside the customer's AWS account and private network boundary. Customer SSO remains authoritative for human identity, workload identity uses short-lived environment-scoped credentials, customer secret management retains provider and MCP credentials, and customer networking controls approved provider egress and MCP access.

Portability is contractual through OpenAI-compatible model access, MCP Connectors, OpenTelemetry, versioned external policy evaluation, stable Agent/Run identity, future workload identity, and customer-owned evidence export. Verified managed-release attestation requires a separate decision. Equal day-one operational support for Azure, GCP, SaaS-hosted, and on-premise environments is deferred until the AWS reference is stable.

Consequences

  • Customer control, execution, telemetry, evidence, and Retrieval data stay inside one customer security boundary except for explicitly approved provider or MCP egress.
  • Identity, secrets, networking, residency, incident response, backup, and recovery integrate with customer operating controls.
  • A concrete reference reduces infrastructure variability while the product and gateway contracts are validated.
  • AWS infrastructure can be first-class in the reference implementation, but cloud-specific primitives cannot redefine resource identity, lifecycle, policy outcomes, Connector classes, evidence, or role behavior.
  • Customers requiring another production topology in the first release are outside the supported reference rather than receiving a nominal but unproven parity claim.
  • Later environment plans must preserve the portable interfaces and demonstrate equivalent control and failure semantics before claiming support.

Current governance mapping

The current source release uses Organizations, Teams, real user/service-account virtual keys and separate human management roles. Agent is managed application content; deployments own secretless execution access and publisher funding. Observe uses Requests, Traces, Sessions and Usage with separate metadata/content/export permissions. Historical identity terms in this target proposal are not the operating contract. See Current release.