Agent Studio at RecVue

A LangGraph multi-agent orchestration layer and its agent harness, built into an enterprise revenue and billing platform.

Team Lead · RecVue · NO PUBLIC DEMO

LED SOURCE · RESUME

Led the team that built an agentic-AI layer into an enterprise revenue and billing platform, and architected the orchestration system underneath it.

The orchestration layer is a graph set with a bounded agent harness around it: a ReAct loop that cannot run away, a human-in-the-loop gate on the decisions that warrant one, circuit breakers on the calls that leave the process, and orphan recovery for the runs that stop mid-flight. Evaluation is heuristic where a rule will do and model-judged where it will not, with budget guardrails on the spend and conversation memory checkpointed into Postgres.

The Agent Studio harness Three bands. Along the top the billing platform writes to an outbox whose committed events reach a partitioned Kafka edge, and only committed events flow down into the harness. The middle band is the harness: a budget guard that can refuse a run before it starts, a bounded plan-act-observe loop over the graph set with a retry counter on its return edge, a circuit breaker on the outward tool call, an evaluation pair of a heuristic and a model acting as judge combining into a verdict, and a human gate every run must pass before commit. The refuse path is severed and returns the run to the loop, so nothing reaches commit without approval. The bottom band holds what survives failure: a Postgres checkpoint, an orphan-recovery watchdog, and a telemetry spine every stage emits into. PLATFORM BILLING PLATFORM OUTBOX KAFKA EDGE the agent layer reads a committed event, never a table mid-write AGENT HARNESS BUDGET GUARD REFUSED GRAPH SET PLAN ACT OBSERVE RETRY · · · CIRCUIT BREAKER TOOL CALL EVALUATION HEURISTIC AS JUDGE VERDICT HUMAN GATE APPROVE COMMIT REFUSE CHECKPOINT ORPHAN RECOVERY revives a run that stopped mid-flight OPENTELEMETRY

Underneath it sits a ground-up rewrite. The legacy Oracle model was replatformed onto PostgreSQL with an outbox-driven core and a streaming edge for the agents, so the agent layer reads a committed event rather than a table it might be mid-write on.

The replatform boundary A box on the left labelled LEGACY ORACLE, a heavy vertical line down the middle labelled OUTBOX, and three lines on the right labelled POSTGRESQL, EVENT CORE and AGENT EDGE. The only line crossing the middle leaves the left box. LEGACY ORACLE REPLATFORMED OUTBOX POSTGRESQL EVENT CORE AGENT EDGE

Evidence

Each line opens with the figure and says what it counts. Every figure is a link into the sources at the foot of this page, and it works with scripts blocked.

  • 10 LangGraph graphs in the orchestration topology
  • 43 nodes across that graph set
  • 390+ tables in the PostgreSQL model of the ground-up rewrite
  • 332 HTTP API groups in the replatformed system
  • 14 schemas in that same model
  • 6 Grafana dashboards in the observability layer
  • 10-engineer team, led on the enterprise billing platform

Where to see it

EMPLOYER SITE · www.recvue.com

Work like this

This is one engagement of several, and the roster compares them all on one ruler. One address reaches him directly.

Talk to Emre about work like this
SOURCES
SOURCE DATE WHAT IT COUNTS
vendor/resume-src/src/identity-public.tex · Work Experience · RecVue · Agent Studio 2026-08-23 Nodes across the Agent Studio LangGraph graph set
vendor/resume-src/src/identity-public.tex · Work Experience · RecVue · Agent Studio 2026-08-23 LangGraph graphs in the Agent Studio orchestration topology
vendor/resume-src/src/experience.tex · Work Experience · RecVue 2026-08-23 Tables in the PostgreSQL model of the ground-up Effect-TS rewrite
vendor/resume-src/src/experience.tex · Work Experience · RecVue 2026-08-23 HTTP API groups in the replatformed revenue and billing system
vendor/resume-src/src/experience.tex · Work Experience · RecVue 2026-08-23 Schemas in that same PostgreSQL model
vendor/resume-src/src/experience.tex · Work Experience · RecVue 2026-08-23 Grafana dashboards in the OpenTelemetry observability layer
vendor/resume-src/src/experience.tex · Work Experience · RecVue 2026-08-23 Engineers on the team led on the enterprise billing platform