Solution Architecture

Users reach CAIPE through Slack, Webex, the UI, or CLI. Keycloak authenticates every path, CAIPE Agent(s) run the request, and AgentGateway routes MCP tool calls after OpenFGA authorization.

CAIPE System Architecture

Harness Engine

Harness Gateway preserves the existing CAIPE chat APIs while routing each authorized agent to either the unchanged Dynamic Agents runtime or the independent Harness Engine. Solid paths are implemented in PR #2401; dashed paths are portable interfaces or sandbox capabilities planned for later work.

Harness Engine system architecture

Editable source: CAIPE system architecture

Source graph

The source graph shows where the compatibility boundary, durable control plane, provider adapters, deployment configuration, contracts, and regression tests live in the repository.

Harness Engine high-level source graph