Venkat AI Platform
Multi-agent orchestration OS
Tradeoff: LangGraph stateful graphs over linear chains — enterprise workflows need checkpoints and HITL.
Metrics loading or API waking…
Applied AI engineering portfolio spanning agent governance, multi-agent orchestration, enterprise RAG, and AgentOps. Every project ships with its architecture diagram, a live platform, and the open-source repository on one card.
Start Here (5 min)
AegisAI → VAP → Enterprise RAG → Content Factory → ADRs (Demo vs Strict labeled). Full checklist →
Eagle-eye org stack
Click into any layer. Metrics pull from public /ops/metrics on Render — architecture decisions backed by running systems, not slide decks.
Multi-agent orchestration OS
Tradeoff: LangGraph stateful graphs over linear chains — enterprise workflows need checkpoints and HITL.
Metrics loading or API waking…
Gateway, policy, HITL, audit
Tradeoff: Control plane over agent builder — enterprises need governance across fleets, not another chat UI.
Metrics loading or API waking…
LLM gateway plane — OpenAI-shaped proxy, stub/BYOK
Demo · metrics on hosted API when deployed
Semantic cache plane — tenant-scoped embed + lookup
Demo · metrics on hosted API when deployed
Access-aware governed RAG
Tradeoff: Authorization before ranking — vector DB is implementation; access control is architecture.
Metrics loading or API waking…
RAG + QLoRA triage pipeline
Tradeoff: RAG for facts, LoRA for schema — never memorize policies in weights.
Metrics loading or API waking…
ASR → LLM → TTS with latency budgets
Tradeoff: Browser ASR on Render; server Whisper opt-in on GPU hosts.
Metrics loading or API waking…
Missions, traces, eval gates
Tradeoff: Missions over monolithic prompts — specialist handoffs with observable traces.
Metrics loading or API waking…
Governed content publish pipeline
Tradeoff: AegisAI gateway blocks publish until policy allows — side effects never bypass governance.
Metrics loading or API waking…
Loop harness · RAG tuning · memory
Tradeoff: Harness + eval loops over bigger prompts — ODAEU tunes RAG on failure.
Metrics loading or API waking…
PagedAttention · continuous batching · KV budget
Tradeoff: Educational simulator before GPU spend — teams learn inference architecture without H100 budget.
Demo · metrics on hosted API when deployed
Multi-agent multi-LLM routing lab
Tradeoff: Self-contained monorepo — no sibling runtime deps; routing is architecture, not a dropdown.
Demo · metrics on hosted API when deployed
Governed intelligence brief · email
Tradeoff: Autonomous inner loop, governed outer loop — only email send goes through gateway.
Metrics loading or API waking…
Usage metering + budget breach detection — gates LLM dispatch across the fleet.
Metrics loading…
Governed AI Reference Stack
Each layer answers a question enterprise agent programs must resolve before production.
What are agents allowed to do?
aegisai-enterprise-agent-platform
How do we route and quota model calls?
aegis-llm-gateway
How do we similarity-cache completions?
aegis-semantic-cache
How do we adapt models to domain format?
domainforge-rag-peft
How do we run real-time voice triage?
voiceforge-assistant
How do we operate agent fleets?
aegisloop-agentops-workbench
How do agents improve?
loop-engine-agent-platform
How do we serve LLMs at scale?
vllm-architecture-lab
How do we answer multimodal asks with the right models?
omniforge
Live Platforms
Each card = decision + signal + limitation + platform + repo
Runtime control plane for agent fleets — gateway, policy, HITL, and audit.
Monitor → Govern → Remediate — a runtime control plane for tool authorization, policy violations, HITL approvals, signed audit, and agent registry lifecycle.
Decision
Control plane over agent builder — enterprises need governance across fleets, not another chat UI.
Signal
Website deploy tools forced through approval_required policy on live platform.
Limitation
Registry defaults to in-memory on free tier; Postgres path documented for production.
What shipped: AegisAI: gateway-first governance control plane →
Multi-agent OS with three orchestrators, seven RAG strategies, and gateway-wrapped delivery.
Three LangGraph orchestrators, seven RAG strategies, loop patterns (ReAct · Reflection · Plan-Execute), and gateway-wrapped delivery to Slack, Telegram, and WhatsApp.
Decision
LangGraph stateful graphs over linear chains — enterprise workflows need checkpoints and HITL.
Signal
16 routed intents · 7 retrieval strategies · AegisAI gateway on notify channels.
Limitation
Vector store optional on free tier; Enterprise RAG adapter bridges to governed RAG platform.
What shipped: Venkat AI Platform: three LangGraph orchestrators live →
Access-aware hybrid RAG with ingest, citations, and optional HITL gates.
Authorization before ranking, hybrid retrieval, cross-encoder rerank, decline-to-answer, citation traceability, AegisAI HITL bridge, and Langfuse trace export.
Decision
Authorization before ranking — vector DB is implementation; access control is architecture.
Signal
golden-eval-registry CI · adversarial suite · JWT Principal when PRODUCTION_STRICT=1.
Limitation
Default live demo is Demo mode (body Principal) with sticky banner; Strict/JWT is the Principal review path (ADR-0006). Free-tier corpus re-ingests after cold start.
What shipped: Golden eval registry gates real CI builds →
Governed support triage — RAG corpus + QLoRA JSON envelope + S0–S2 eval compare.
End-to-end support triage: capstone SOP RAG, Bitext QLoRA + DPO, S0→S4 eval ladder, Ollama bench UI, adapter registry — RAG holds facts, PEFT holds JSON discipline.
Decision
RAG for facts, LoRA for schema — never memorize policies in weights.
Signal
S0→S4 compare · DPO preference win-rate · `/bench` Ollama metrics UI · `VLLM_BASE_URL` Path B.
Limitation
Mistral QLoRA requires GPU; Render API uses mock/template baseline unless Ollama/vLLM Lab wired. Path B is educational (not CUDA multi-LoRA).
What shipped: DomainForge: RAG + QLoRA support triage pipeline →
Closes portfolio Pillar 5 — measurable ASR / LLM / TTS latency with honest free-tier defaults.
Browser-first ASR on Render free tier, pluggable LLM (mock / Ollama / DomainForge), edge-tts with browser fallback, per-phase latency waterfall, and graceful degradation to text.
Decision
Browser ASR on Render; server Whisper opt-in on GPU hosts.
Signal
9-test CI · P50/P95 latency waterfall UI · phase budgets (ASR/LLM/TTS).
Limitation
Browser ASR quality varies; mock LLM default on Render until Ollama host wired.
AgentOps workbench — bounded missions, traces, eval gates, and human-gated ship.
Bounded missions, specialist handoffs, observable traces, source coverage scoring, FinOps estimates, Langfuse spans, and human-gated ship paths.
Decision
Missions over monolithic prompts — specialist handoffs with observable traces.
Signal
mission_gate CI suite · P50/P95 + failure rate on /api/metrics.
Limitation
Postgres persistence optional; mission history resets on in-memory backend.
What shipped: AegisLoop: mission fleets with eval gates →
Governed content pipeline — research, multi-platform drafts, HITL, then publish.
Research → five platform drafts → HITL review → governed publish through AegisAI gateway, OAuth adapters, and scheduled cron pipelines.
Decision
AegisAI gateway blocks publish until policy allows — side effects never bypass governance.
Signal
Real LinkedIn/X OAuth publish path when tokens configured.
Limitation
Clerk keys required for full pipeline; invite-only signup in production config.
What shipped: AI Content Factory: governed multi-platform publish →
Self-improving agents — clone repos, run pytest, patch, and open PRs.
Agent → Harness → Loops → Memory. LangGraph coding loop (Orchestrator · Review · Quality), ODAEU RAG tuning, and repo fix workflow: clone → pytest → patch → branch → PR — never pushes to main.
Decision
Harness + eval loops over bigger prompts — ODAEU tunes RAG on failure.
Signal
repo_fix suite in golden-eval-registry · never pushes to main.
Limitation
Requires GitHub token for repo fix loop; Groq API for agent inference.
What shipped: LoopForge: clone → pytest → patch → PR workflow →
Interactive vLLM architecture explorer — PagedAttention, batching, KV budget, adapter chat.
Educational vLLM reference: PagedAttention, continuous batching, KV budgets, multi-LoRA economics — pairs with DomainForge adapter training (ADR-022).
Decision
Educational simulator before GPU spend — teams learn inference architecture without H100 budget.
Signal
Live simulator · KV budget calculator · DomainForge↔vLLM Path B (ADR-022 Accepted).
Limitation
Simulator + educational adapter swap — not CUDA multi-LoRA kernels or production SLAs.
What shipped: vLLM Architecture Lab: PagedAttention explorer →
Overnight intelligence brief — nine sources, snapshot diff, eval gate, governed email.
Allowlisted HN, arXiv, and industry RSS → snapshot diff → executive brief → eval gate → AegisAI gateway email — autonomous inner loop, governed outer loop on mail only.
Decision
Autonomous inner loop, governed outer loop — only email send goes through gateway.
Signal
brief_gate eval · durable archives in /reports · nightly-smoke CI.
Limitation
Render cold start may delay first live run; archives prove report UX without a fresh cron.
What shipped: Sentinel Brief: governed overnight intelligence brief →
Multimodal ask with proven multi-LLM routing — waterfall shows which model ran each step.
Self-contained multimodal multi-agent multi-LLM platform — text, image, and voice fan out across agents and MCP tools; task-class routing with a live model waterfall and A/B proof.
Decision
Self-contained monorepo — no sibling runtime deps; routing is architecture, not a dropdown.
Signal
Live demo · /v1/ask waterfall · /v1/ask/ab · ADR-027
Limitation
Render cold start on free tier; mock fallback when cascade misses; clean omniforge.vercel.app may need SSO off.
Mock system design and behavioral interviews with dual LLM judges.
Sectioned system-design forms, STAR behavioral practice, and reasoning trade-offs — graded by OpenAI and Anthropic against Staff+/Principal rubrics. Bring your own API key; keys never touch our servers.
Decision
Per-question rubrics over generic chat — grading matches playbook depth.
Signal
139/140 live cases passed · judge disagreement shown, not averaged away.
Limitation
Requires user's OpenAI or Anthropic API key; no server-side key storage.
What shipped: Practice Arena: 35/35 interview playbook coverage →
Six suite kinds (RAG answer, harness QA, repo fix, mission gate, graph HITL, brief gate). Enterprise RAG and AegisLoop fail builds on regression — not just validate fixtures. Running one suite for the first time found and fixed a real bug in its own fixture.
Architecture Decisions
Canonical ADRs and case studies live in the GitHub architecture portfolio— browse trade-offs before forking code. Architecture theses →
Canonical Essay
Why VAP and AegisAI are complementary layers — not competing products.
Read the full architecture storyFrom Multi-Agent OS to Agent Governance
VAP answers what agents should do. AegisAI answers what they are allowed to do. The portfolio ships both — wired together through gateway SDK, HITL overrides, and signed audit — because enterprise programs need both layers from day one.
Proof: Live integration: VAP notify · RAG ingest · Content Factory publish · AegisLoop ship
RAG is not retrieval infrastructure
Enterprise RAG filters by principal clearance and group membership before ranking — then hybrid retrieval, reranking, graph expansion, and citation traceability. Vector DB selection is an implementation detail; authorization-before-ranking is the architecture decision.
Proof: enterprise_rag_platform · enterprise-rag-platform-eta.vercel.app
AgentOps is how fleets survive production
AegisLoop models bounded missions with specialist handoffs, source coverage scoring, evaluation gates, FinOps estimates, and human-gated ship — the operating layer between orchestration platforms and production agent fleets.
Proof: aegisloop-agentops-workbench.vercel.app
Curriculum patterns teach the loops — platforms govern them
Five MIT-licensed curriculum stubs with animated trace demos on Vercel. Not production fleets — they map ideas into VAP / Content Factory governed graphs. Status tables mark stub LangGraph and no gateway.
Proof: 5 live trace viewers · Curriculum Agent Patterns series
Loop engineering is the next layer
LoopForge implements Agent → Harness → Loops → Memory: LangGraph repo fix (clone → pytest → PR), ODAEU RAG tuning, and procedural memory — live on demo-omega-taupe.vercel.app + loopforge-api.onrender.com.
Proof: demo-omega-taupe.vercel.app · loopforge-api.onrender.com
2026 Agent Protocol Stack
MCP for tool access, vpeetla-ai-skills for engineering discipline, AegisAI for side effects, trace-linked LLMOps (Langfuse/OTel) for evals on the same trace_id. ADR-007 documents how platform repos compose for production agent deployments.
Proof: vpeetla-ai-skills · ADR-007 · ORG_IMPROVEMENT_PLAN_2026
Free stack, production boundaries
Every live demo runs on free-tier infrastructure with explicit service boundaries: UI on Vercel, APIs on Render, LLM via Groq, vectors via Qdrant Cloud, cache via Upstash — the same pattern I publish in Building Multi-Agent Systems on a Free Stack.
Proof: 15 live products on Vercel + Render free tier
10→2
Agent ops staffing reduction (targeted flows)
Multi-$M
Revenue & savings — payments, subscriptions, EDI
14 live
Reference systems with platforms
29 ADRs
Documented architecture decisions
Architecture Decision Records
VAP + AegisAI as complementary layers — orchestration without governance is a liability.
RAG is an access-controlled intelligence layer, not a vector DB wrapper.
Bounded missions with eval gates — fleets survive production, not monolithic prompts.
Side-effecting tool calls require policy + human approval + signed audit.
Vercel + Render + Groq — production boundaries without enterprise budget on day one.
Self-improvement belongs in harness + eval + memory — not bigger system prompts.
Skills, MCP, gateway, and trace-linked observability as one four-layer stack, not ad hoc wiring.
LinkedIn/X get real OAuth publish; platforms with no public API get honest copy-draft export instead.
Chat, orchestrator, ingest, RAG, and thread routes now require a caller identity, not just a claimed one.
Closed the same gap independently in both the FastAPI backend and the Netlify serverless function.
Real cost governance needs one shared ledger, not per-repo fragments — built as its own repo, not logic bolted onto two existing ones.
A shared cost-governance service only matters once it's actually called — real usage now halts real agent dispatch in both AegisAI and AegisLoop.
A gateway that only gates outbound MCP calls is half a protocol — AegisAI now exposes governed tools via MCP too, and AegisLoop is the org's first client to actually discover-then-invoke VAP's real A2A surface.
Fixtures existing and fixtures being correct are different claims — running one suite for the very first time against a real pipeline found and fixed a genuine bug in the fixture itself.
Terraform files nobody ever ran aren't infrastructure experience — a real apply, a real budget breach against a real database, a real orchestrator run against a real load balancer, then a real teardown confirmed empty by each cloud's own CLI.
Validation logic that gets computed and then discarded isn't a data contract — enterprise_rag_platform now rejects bad ingests instead of silently indexing them, and found a whole CI test file that had never actually run along the way.
Most AI-architect interview prep is generic; this repo's 14 entries either cross-link to a real shipped decision in this org or say plainly that they don't.
Case Studies
Runtime control plane — gateway, HITL, signed audit
Includes live demo link →
3 LangGraph orchestrators · 7 RAG strategies
Includes live demo link →
Authorization before ranking · hybrid retrieval
Includes live demo link →
Mission fleets · eval gates · FinOps · Langfuse
Includes live demo link →
Research → drafts → HITL → governed publish
Includes live demo link →
LangGraph repo fix → PR · ODAEU RAG tuning · MCP · memory
Includes live demo link →
PagedAttention · continuous batching · KV budget simulator
Includes live demo link →
Why VAP and AegisAI are complementary layers
10→2 staffing in targeted supply-chain flows
Multi-$M annualized revenue impact
Durable recurring revenue platform
Multi-$M annualized savings
Agent Patterns
Mapped to VAP orchestrators — inspectable, not abstract.
ReAct
Thought → action → observation loops with bounded iterations and tool contracts.
Used in: VAP Deep Research orchestrator
Reflection
Critique-and-revise before delivery — quality gates for draft-heavy copilots.
Used in: VAP Research + Architecture pipelines
Plan-Execute
Explicit planning phase before tool execution — safer multi-step enterprise workflows.
Used in: VAP Architecture Review orchestrator
Multi-Agent
Orchestrator-controlled collaboration with reviewer gates before final output.
Used in: VAP Platform orchestrator + specialists
Swarm
Parallel specialist exploration with handoff-friendly agent boundaries.
Used in: VAP parallel asyncio bundles
Open Source
Platform Repositories
View all on GitHubvLLM architecture lab — PagedAttention simulator, continuous batching scheduler, KV budget API, and interactive 5-tab architecture explorer.
Live demoOrg-wide agent skills for Cursor and Codex — MCP, gateway, loop engineering, TDD, honest status tables, vLLM inference.
Versioned golden fixtures for the governed agent stack — portable, reviewable eval contracts so Enterprise RAG, LoopForge, AegisLoop, and Content Factory can prove they don't regress, not just demo.
An LLM-as-judge mock-interview tool covering all 35 questions in the interview playbook -- sectioned system-design forms, full STAR practice for behavioral questions, and framework-plus-example for reasoning trade-offs -- graded by both OpenAI and Anthropic against each entry's own real Staff+/Principal rubric, bring your own API key, never stored on or sent to our servers.
Live demoLoopForge — self-improving agent harness. LangGraph repo fix → GitHub PR, ODAEU RAG tuning, MCP tools, procedural memory. Agent → Harness → Loops → Memory.
Live demoEnterprise agent governance control plane — gateway SDK, policy violations, HITL approvals, signed audit, agent registry, and governed orchestrators.
Live demoReal, enforced cost governance for AI agent fleets — usage metering, budgets, and breach signals as a shared service, wired into both repos that used to fake it.
Principal-architect multi-agent OS — 3 LangGraph orchestrators, 7 RAG strategies, loop patterns, and gateway-wrapped delivery channels.
Live demoProduction RAG as a governed intelligence system — access-aware retrieval, context engineering, evaluation, guardrails, and operational decision records.
Live demoMission fleets with evaluation gates — bounded missions, specialist handoffs, traces, FinOps, Langfuse spans, and human-gated ship paths.
Live demoMulti-agent content pipeline — research, five platform drafts, HITL review, governed publish (real LinkedIn/X OAuth; other platforms export a copy-ready draft).
Live demoAgent Pattern Library (GitHub)
Staff+ interview study notebook — AI/ML system design, classic distributed systems, cloud architecture, coding, interview craft, and STAR prep — hellointerview-style depth with a live table/notebook UI.
Centralized multi-agent architecture with specialized roles, orchestrator control, shared context, and reviewer gates before final output.
ReAct pattern for tool-using assistants with bounded iterations, schema-light tool contracts, and separation between reasoning and execution.
Plan-then-execute agent workflow for decomposing complex tasks into reviewable steps before tool execution begins.
Self-critique and revision loop for improving agent output quality before responses reach users or downstream systems.
Swarm-style agent coordination for parallel exploration, specialist handoffs, and emergent task routing across agent roles.
Enterprise Delivery
Lucid Motors · Automotive Manufacturing · 2023–Present
Enterprise teams needed AI automation beyond demos — repeatable operational work with governance, evaluation, and observability.
Volvo Cars · Automotive & Global Commerce · 2019–2023
Regional payment coverage needed to support Gulf-market transactions with better gateway fit, reliability, and revenue enablement.
Volvo Cars · Automotive Digital Commerce · 2019–2023
Core product lines needed recurring revenue capabilities rather than relying only on transactional commerce patterns.
Volvo Cars · Automotive Supply Chain · 2019–2023
License-heavy SAP and TrueCommerce EDI workflows created recurring cost, integration friction, and limited engineering ownership.
The intellectual rhythm behind the code — weekly architecture essays on Substack and this blog.
Architecture portfolio (GitHub)Read architecture writing