Section navigation
AAExample Conforming DeploymentABExample Conformance StatementACExample Record Surface MapADExample Configuration MatrixAEExample Multi-Vendor WorkflowAFExample Discovery AssessmentAGExample Feedback Routing TableAHExample Legal Hold ProcedureAIInternational Legal Sector GuidanceAJEmergent Autonomous Execution in a Web Research DeploymentAKMCP Integration with Regulated Financial InfrastructureALAcquisition Modality Landscape for Retained Interaction RecordsAMMobile Agent WorkflowANHealthcare Revenue Cycle Agent WorkflowAOEnterprise Governance Interceptor Workflow

Annex AE: Example Multi-Vendor Workflow

ARCS v1.0

STANDARD ANNEX AE

March 2026 | Informative Annex

Classification: Tier 1 / Standard Annex / Informative

Standard Annex AE: Example Multi-Vendor Agent Workflow

Illustrative Interaction Record Propagation (Informative)

This annex illustrates how interaction records propagate across systems during a multi-vendor agent execution. This annex is informative.

AE.1 Workflow Steps

Step 1 (User Input): User enters prompt. Records: prompt text, session log, UI history. Surfaces: tenant storage, provider log, browser cache. Custodians: user, operator, provider.

Step 2 (API Call): Application sends request to model provider. Records: API request log, inference log, monitoring log. Surfaces: provider storage, cloud log, monitoring service. Custodians: provider, cloud.

Step 3 (Agent Planning): Agent decides to call tools. Records: plan trace, routing decision, tool selection log. Surfaces: agent runtime, provider log. Custodian: provider. Section 16.

Step 4 (Tool Call): Agent calls plugin. Records: tool request, tool response, tool log. Surfaces: plugin vendor, provider, monitoring. Custodians: vendor, provider, cloud. Section 15.

Step 5 (Retrieval): Agent retrieves file. Records: retrieval query, document copy, access log. Surfaces: document system, provider, monitoring. Custodians: operator, provider, cloud.

Step 6 (Output): Model produces output. Records: output text, response log, safety log. Surfaces: provider, tenant, monitoring. Custodians: provider, operator.

Step 7 (Feedback): User clicks thumbs down. Records: feedback record, review copy, evaluation sample. Surfaces: feedback system, review system, evaluation dataset. Custodian: provider. Section 11.

Step 8 (Derived Record): User copies output to document. Records: document, email, database entry. Surfaces: document server, email server, local device. Custodians: operator, user. Section 17.

Step 9 (Backup): System backup runs. Records copied: tenant DB, logs, documents. Surfaces: backup, snapshot, archive. Custodians: cloud, operator. Section 18.

Step 10 (Legal Hold): Litigation hold activated. Effects: deletion disabled, backups preserved, archive preserved, provider notified. All surfaces affected. ARCS-PV preservation controls apply.

AE.2 Resulting Record Surface

Twelve surface categories: provider storage, tenant storage, user device, plugin vendor, monitoring, feedback system, evaluation dataset, document system, backup, archive, snapshot, cache. Custody fragmented across six parties. Discovery surface broad.

AE.3 Governance Requirements Triggered

Property Section Level Required

Multi-vendor surfaces 15 Level 4+

Agent runtime records 16 Level 5

Feedback routing 11 Level 3+

Derived records 17 Level 5

Backup persistence 18 Level 5

Custody fragmentation 8 Level 2+

Preservation override 14 Level 4+

Configuration effects 19 Level 3+

This workflow requires Level 4 or Level 5 conformance.

ARCS v1.0 | Annex AE: Example Multi-Vendor Agent Workflow | March 2026 | Informative