02 — Architecture¶
Status: Current | Last reviewed: 2026-10-20
How the system is shaped, end to end. Read these in order if you are new; jump to the lifecycle that matches your work if you are not.
- Agent Studio architecture map — interactive diagram of the authoring control plane, shared tenant state, the conversation runtimes, and the telephony edge. Source spec: agent-studio-architecture.json.
- Salesforce multilingual email operations — high-level interactive map of Salesforce email ingress and egress, durable Case data, Agent Studio automation, and the record-backed agent experience. Source spec: salesforce-email-agent-studio.architecture.json.
- Runtime targets — Vanguard, Sentinel, customer clusters.
- Voice request lifecycle — what a phone call looks like.
- Agentforce Voice companion forms — Salesforce developer handoff for the ACG auto demo, Apex/MCP actions, bounded form checks, and validation limits.
- Salesforce-native auto companion — separate Apex/LWR prototype, native messaging, passwordless verification and shared form state.
- Chat request lifecycle — what a text conversation looks like.
- Personal Agent Protocol adoption — draft proposal for assistant access, customer delegation, durable conversations and transactional operations.
- Async request lifecycle — how triggered workflows run.
- Workflow agent expansion and startup latency — source assessment, isolated graph timings, routing/guardrail options, specialist teams and external client integration. Draft analysis.
- Data model —
agentsvsagent_versions, surfaces, conversations. - Headless presentation decisions — selected architecture for OpenAI Decisions to choose behaviors, component compositions and placement; runtime integration pending.
- Multi-tenancy — how tenants are isolated.
- Analytics Agents from CallSight — original source assessment and migration design, with links to the implemented runtime.
- Analytics question and result parity — required question coverage, all original tools, acceptance scenarios, conversational comparisons and performance gates.
- Analytics compiler hierarchy and CallSight parity — implemented annotation and report stages, configurable hierarchy, detection and dependency-aware refresh.
- Analytics migration validation — executed source comparisons, migrated datasets, visual checks, model choices and measurement limits.
- Analytics chat catalogue and CallSight parity — recorded demo journey, per-agent landing briefings, catalogue reuse, ordered responses and visual verification.
- SIP edge modularization — standalone SIP edge, pluggable voice runtimes (Bedrock AgentCore),
agentcore-sdkexport. Draft analysis. - Pipecat-native alignment — homegrown multi-agent machinery vs pipecat 1.4 workers/bus/jobs, plus the horizon-agent layering across ai-orchestrator and async-agent. Draft analysis.
- A2UI spec convergence — the shipped A2UI dialect vs a2ui.org v0.9.1/v1.0, and where wire compliance pays off. Draft analysis.
- Context-efficiency backlog — the large/hot files, their measured churn, proposed split seams, and the tests that assert on source structure. Read before proposing a refactor.