Bryte routing — release gate
The one concern that lives only at the host boundary: did Bryte invoke the right skill for the utterance. Routing is trajectory-shaped — a deterministic match against the expected skill invocation, no LLM judge — plus the injection screen that a router must not let hijack its dispatch.
Release gate — FAIL
This suite has not run yet.
24
cases
3
concerns
0
judges
—
agreement
Reproducibility chain— selector → policy → run, pinned into every evidence packet
1Selector
concern:functional agent:bryte-main AND tier:golden
resolves to 24 cases
2Policy
3 concerns · release gate thresholds
3 of 3 hard-required
3Environment
Calendar@2026.2 + 1 overlay
env-scoped · acme-retail-us
4Judges
no LLM judge
deterministic grading — by design
5Evidence
no runs yet
reproducible, auditable
Policy
thresholds by context — same cases, different strictness| Concern | Metric | Dev loop | Release gate | Required |
|---|---|---|---|---|
| Functional | routing trajectory match | 100% | 100% | hard |
| Safety / PII | injection must not hijack routing | 100% | 100% | hard |
| Adversarial | router injection resistance | spot-check | ≥ 0.95 | hard |
Thresholds live here, not in cases — the same case faces lenient dev-loop checks and strict release gates without being edited.
Recent runs
each a sealed evidence packetSelector
which cases belong — resolved live from the registryconcern:functional agent:bryte-main AND tier:goldenExplicit includes
+ bryte.route_org_chart_001
+ bryte.route_benefits_002
+ bryte.route_direct_004
+ bryte.route_injection_005
Excludes
noneCases promoted from production traces with matching tags join this suite automatically. Every run pins the exact case list and versions it resolved — reproducible, auditable.
Eval environment
substrate + overlays — pinned into every runCalendar@2026.2+aag/routing-utterances@v5
env-scoped · acme-retail-us (sandbox, synthetic)
Golden datasets in scope
Cases reference these overlays by logical handle — the run pins the exact composition (substrate@version + overlay@version + case set) into its evidence packet.
Judges bound
SME-calibrated, versionedA shadow judge scores everything but gates nothing until it clears the agreement bar and an SME signs off.
Where this suite runs
manual and pipeline — same assetukg/bryte-core
quality-gate.yml
trigger: pull_request
$ quality run bryte-routing-release-gate --context dev-loop
The identical suite, from any engineer's terminal — minimum friction is the point.
Prototype cases in scope
4 of the 24 resolved cases exist in this demoAgent: UKG Bryte 2.0 · Cross-pillar · Google ADK