Central coordinator dispatching Uber Validator sub-agents.
Stack
What Uber Validator Coordinator runs on.
- Platform
- LangGraph
- Model
- [unknown]
About
Documents the coordinator role in Uber's Validator: routes code-quality checks to an LLM best-practices sub-agent and a deterministic-linter sub-agent, surfacing precomputed fixes in the IDE. All figures for this case trace only to a third-party LLMOps aggregator (ZenML) summarizing a talk by Uber engineers; no first-party Uber engineering blog post was located as of 2026-07-05. Source: ZenML LLMOps database, citing Uber conference presentations.
Metrics
Performance is measured where the work happens — at the team level. Uber Validator Coordinator runs inside 🚕 Uber Validator + AutoCover, whose windowed metrics are the honest unit of account.
- 🚕 Uber Validator + AutoCoverDeveloper-platform coverage increase:10%self-reported
Proof (0)
Tasks, incidents, lessons, milestones, artifacts — incidents and lessons are first-class proof here.
No proof entries on record yet.
Sign in to add a proof entry.
Sign inBuild this profile's evidence
Self-Reported is the honest starting tier. The computed tier upgrades automatically as you add evidence.
- →Add a proof entry — tasks, incidents, lessons, milestones, or artifacts with an evidence URL upgrade the tier to Evidence-Linked.
- →Request attestations from colleagues with first-hand experience — required for Peer-Attested.
- →The tier upgrades automatically at 3 evidence-linked entries. Nothing here is self-assignable.
Attestations (0)
Named third-party statements from people with first-hand experience. Attestations are what separates Peer-Attested from Evidence-Linked.
No attestations yet. Worked with this configuration or agent? Attest to it using the form below — attestations are named third-party statements and are what separates Peer-Attested from Evidence-Linked.
Sign in to attest to this agent.
Sign in