SERVICE · 04

A2A Orchestration

Typed message-passing between specialized agents. Mesh observability without manual instrumentation.

WHAT YOU GET

Typed envelopes

Every agent-to-agent message has a versioned schema. Wire it once; codegen handles the rest.

Auth between agents

mTLS + scoped tokens by default. Every call carries a trace ID for audit.

Mesh observability

Cross-agent traces stitched automatically. Find the slow agent in 1 click.

02 · Reference architecture

What we actually ship.

Every system we build follows this shape. Client at the edge, tools in a sandbox, traces everywhere, evaluators gating output. No black boxes, no "it works on my machine."

EDGE
Client
web · mobile · API
Gateway
auth · rate-limit · PII redact
ORCHESTRATION
Orchestrator
planner · router · memory
Durable · exactly-once
AGENTS & TOOLS
Retrieval
hybrid · rerank · cite
Tool calls
sandboxed · timeboxed
Evaluator
gates · rubrics · LLM-judge
DATA & TRUST
Vector + BM25
tenant-isolated
Traces / logs
OTel · replayable
Signed output
auditable · rollback
04 · Run

Watch an agent do the job.

Three real production scenarios, replayed at observed latency. Every box is a span; every span has tokens, cost, and an eval gate. This is what shows up in your traces, not a marketing animation.

POST/api/v1/agent/runTrade desk submits a €4.2M block trade. Agent must reject, approve, or flag in <3s.
trace · compliancespan_id 7c1f…
orchestrator.run0ms
PLANorchestrator.planorchestrator · 80ms · 184 tok · $0.0014
Plan rationale

Pretrade review requires: applicable-rules retrieval, market-data lookup, position-check, and a deterministic evaluator gate.

Subtasks
retrievaltool.market_datatool.position_checkevaluator
0ms/1.82s
LATENCY0msbudget 3.00s
TOKENS0in + out
COST$0.0000budget $0.025
EVAL GATEdeterministic + LLM-judge
APPROVED · 1 flag
Trade clears 11 of 12 rules. Rule 23.2 (book concentration) flagged for desk-head sign-off.
latency2.41scost$0.014tokens1,827evals12/12
09 · STACK

Modern tools, composed cleanly.

Models
Claude, GPT-4, Llama 3
Auth
Clerk, Auth0
Orchestration
Workflows, sagas
Messaging
NATS, SQS, typed envelopes
10 · FAQ

FAQ · A2A Orchestration

Two-week shadowing during ramp, runbook + eval suite delivered in your repo, oncall overlap for the first incident. After that you own it.

Each agent has a typed identity + mTLS by default. We use scoped tokens with short lifetimes; calls between agents carry trace IDs so the auditor can reconstruct the flow.

START

Ship the first system.

Fixed-price discovery in 2 weeks. You leave with an architecture, a working spike, and a build plan.