bryte.route_org_chart_001
validv1goldenauthoredRoute “take me to the org chart” to People Navigator — UKG Bryte 2.0 (Google ADK)
ukg/bryte-core · evals/cases/bryte.route_org_chart_001.yaml@ d41f7a0PR #88 · reviewed
One asset → 1 backends— routed centrally by AAG · each grader runs on exactly one engine, so nothing is scored twice
portable-v1 · authored once
bryte.route_org_chart_001
“Take me to the org chart”
1 concerns · 1 YAML asset · ukg/bryte-core
Functional
→ ADK eval
functional@v3 · in-sync
The assertion
Routed to People Navigator.
Golden context
expected_tools · in_order
route_to_skill
Compiled → 1 targetsbryte.route_org_chart_001.functional.config all in-sync
Portable eval case
portable-v1input
“Take me to the org chart”
entities
overlay handles — never raw substrate IDs
employees.org_member_default→ E-11002 · via aag/routing-utterances@v5 on Calendar@2026.2expected_tools
order: in_order
- 1
route_to_skill{"skill":"people-navigator"}
expected_output
Routed to People Navigator.
metadata
pillar:platformtier:goldenroutingsensitivity: syntheticpersona: employee
datasets
pinned compositions this case belongs to
kind
drives grader packs
FunctionalTool trajectory, response match, and semantic regression bulk.
Graders
inherited from AAG packs via kind: — each routedFunctionalfunctional@v3inherited→ ADK eval
tool_trajectoryin-order tool match
response_semanticLLM judge
response_lexicalROUGE-1
Routed, not replicated. Each grader goes to exactly one backend. Nothing is forced onto a backend that cannot express it, and the same case is never scored twice for the same thing.
Routing
concern → backend · centrally owned by AAG| Concern | Backend | Why this backend |
|---|---|---|
| Functional | → ADK eval | Native to the agent runtime — owns the regression bulk (trajectory, ROUGE, semantic judge). |
Compiled output
1 routed targetsArtifacts generated per routed backend (full compiled view shown on the hero case, hr.policy_carryover_004):
FNbryte.route_org_chart_001.functional.config→ ADK evalin-sync