cleandataengineering.aiAgent Harness, drawn simply
You are here: Architecture › The big picture › Assets and families

Agent Harness Tutorial · Architecture

The horizontal assets and the five families

The concerns fall into five families. Each family becomes a few horizontal assets that our platform team builds once on Azure and every agent reuses.

Cells with a small circle open the design page for that concern.
FamilyAssetWhat every agent getsOn AzureOwner
ThinkModel gatewayany model, one doorAPIM AI gateway → Foundry ModelsPlatform
ThinkKnowledge & retrievalpolicy wordings, SOPsPostgreSQL + pgvectorPlatform + data
ThinkMemory & statecase, sessionAzure Database for PostgreSQLPlatform
ActTool / MCP hubtyped actionsMCP servers on Container Apps + APIMPlatform + domain teams
ActA2A handoffagent to agentA2A endpoints on Container AppsPlatform
ActChannel adapterschat, WhatsApp, emailCommunication Services · Chatwoot · TeamsPlatform + CX
ControlIdentity & secretsagents get own IDsEntra · managed identity · Key VaultSecurity
ControlGuardrails & policyrules as codeContent Safety + our positioned rulesSecurity + risk
ControlHuman desk & approvalsapprovals, handoffDBOS / Temporal + Teams cardsPlatform + operations
SeeObservability & replaytrace, replayApp Insights · Managed Prometheus · GrafanaPlatform + SRE
SeeCost controlbudget per agentOur meter · APIM token limits · Cost ManagementPlatform + FinOps
ChangeEval librarygolden sets, red-teamGitHub Actions · Foundry evaluationAssurance team + QA
ChangeRelease & configversions, rollbackApp Configuration · revisions · ACRPlatform
ChangeAgent registrywho exists, which versionAPI Center + catalogue in GitArchitecture board

Want every detail? The long version is in the Series: the horizontal assets.