Mission Control Product Documentation

Target architecture — not the current operating contract

This library preserves product direction. For available behavior and procedures, see the current release and planned capabilities.

This archive holds product design, planned capabilities, and architecture decisions. It remains available at its existing URLs, but is excluded from documentation search and the current-guide AI index. Use the task guides for supported behavior.

Authority

The target architecture overview and accepted architecture decisions govern product-direction boundaries. Documents here explain individual parts of that direction and must not redefine those boundaries independently.

Documentation map

• Product vision
• Product principles
• Glossary
• Product backlog

Architecture

• Overview
• Control kernel
• Enforced gateways
• Resource and evidence model
• Deployment and security
• Reliability and failure semantics

Product modules

• Agent Studio
• Automations
• AI Applications
• Retrieval
• Connectors and MCP catalog
• Model management

Operations and assurance

• Governance and Policy Studio
• Approvals — implemented as rules and durable tool approvals; see Approvals in the administrator guide
• Observability and evaluation
• Evidence and assurance

Product experience

• Information architecture
• Roles and journeys
• Design system

Architecture decisions

• Decision index

Document ownership

• Product positioning and boundaries: vision.md and principles.md.
• Cross-platform component contracts: architecture/.
• Module responsibility and connections: modules/.
• Governance, evidence, and operating behavior: operations/.
• Navigation, roles, journeys, and visual language: experience/.
• Durable architectural choices: decisions/.

For design decisions within this archive, use the target architecture and accepted architecture decisions. For supported behavior, the current release and current task/reference guides take precedence.

Historical sales collateral and superseded design narratives are not published product authority.

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.