Architecture overview

The Gateway coordinates governed access to supported business operations.

The platform separates the user interface, AI interaction, and connected-system execution. Organization and workspace context, authorization, policy, approval, and recorded outcomes are handled through the Gateway and its service boundaries.

The request journey

  1. Resolve the authenticated user, organization, workspace, and permitted capabilities.
  2. Supply available business knowledge, conversation context, and supported tool descriptions.
  3. Interpret the request and validate proposed tool inputs.
  4. Evaluate access and configured policy, including confirmation or approval when required.
  5. Execute through the supported connection and report the recorded outcome.
  6. Make relevant request, decision, and execution evidence available for inspection.

Generic platform, specific integrations

Core operations are modeled through connections and capabilities. Vendor and business behavior belongs in connectors, domain configuration, and extensions. A store refund is an example of a connected operation, not a built-in platform domain.

Current boundary

AI Ops remains under development and release qualification. OpsPilot is a standalone earlier prototype; its simulated store integrations and public role selector do not share the Gateway’s authorization or execution path.