Repo Map

Core Subsystems

src/semantic-router/
- Go router, Envoy extproc server, config loading, Kubernetes controller, routing logic
src/vllm-sr/
- Python CLI, config generation, Docker orchestration, local bootstrap flow
candle-binding/, ml-binding/, nlp-binding/
- Rust-backed inference and ML bindings used by the router
dashboard/
- Dashboard frontend and backend
deploy/operator/
- Kubernetes operator, CRD schema, and controller-facing deployment contract
src/training/
- classifier/post-training scripts, training utilities, and evaluation-oriented model workflows
e2e/
- kind/Kubernetes E2E framework and profile matrix
tools/make/
- canonical automation entry points
tools/agent/
- coding-agent manifests, scripts, skills, and structure rules

src/semantic-router/pkg/config/config.go
- central config type table; prefer moving plugin contracts and helper methods into adjacent files
src/semantic-router/pkg/extproc/processor_req_body.go
- request-body orchestration hotspot; prefer extracting narrow helpers instead of extending the main flow
src/semantic-router/pkg/extproc/processor_res_body.go
- response-body orchestration hotspot; keep parsing, caching, and replay helpers separate
dashboard/frontend/src/pages/ConfigPage.tsx
- dashboard config editor hotspot; keep schema/types/helpers outside the page component when possible
dashboard/frontend/src/pages/SetupWizardPage.tsx
- setup route hotspot; keep route state in the page but move wizard support types, config builders, and step panels into adjacent modules
dashboard/frontend/src/components/ChatComponent.tsx
- playground/chat orchestration hotspot; keep cards, citation rendering, and control widgets in adjacent components
dashboard/frontend/src/components/ExpressionBuilder.tsx
- expression editor hotspot; keep AST/tree helpers and reusable render fragments outside the main ReactFlow container