plano/crates
Adil Hafeez 5b869648c4 remove random selection policy — consumers can shuffle client-side
Plano should only handle ranking that requires server-side data
(cost metrics, latency). Random shuffling is trivial for callers.
2026-03-30 12:33:06 -07:00
..
.vscode use standard tracing and logging in brightstaff (#721) 2026-02-09 13:33:27 -08:00
brightstaff remove random selection policy — consumers can shuffle client-side 2026-03-30 12:33:06 -07:00
common remove random selection policy — consumers can shuffle client-side 2026-03-30 12:33:06 -07:00
hermesllm adding new supported models to plano (#829) 2026-03-15 12:37:20 -07:00
llm_gateway Unified overrides for custom router and orchestrator models (#820) 2026-03-15 09:36:11 -07:00
prompt_gateway Rename all arch references to plano (#745) 2026-02-13 15:16:56 -08:00
build.sh Use mcp tools for filter chain (#621) 2025-12-17 17:30:14 -08:00
Cargo.lock [ISSUE 706]: Standardize returned errors from Plano (#772) 2026-02-24 14:34:33 -08:00
Cargo.toml use standard tracing and logging in brightstaff (#721) 2026-02-09 13:33:27 -08:00