GIOS Studioalpha · read-only
Preferred provider
Provider selection plan — WHICH provider executes this authorized request, and how is it routed? Deterministic filtering + ranking over the provider registry, with a failover chain. Executes nothing; the future Execution Runtime (V5) consumes this plan.
selected→ google-geminiblockfailovercost mediumbinding: false#a25e51fb
Routing decision (fail-closed)
provider_selectedroute
selected "google-gemini" (priority 3, cost medium); 8 fallback(s)
Failover chain
google-gemini → anthropic-claude → openai-gpt → nvidia-nim → deepseek → ollama → lm-studio → mcp-provider → local-runtime
Selection & handoff (V5 readiness only)
Selected provider
providergoogle-gemini
matched capabilitiestext
context limit1000000
fallbacksanthropic-claude, openai-gpt, nvidia-nim, deepseek, ollama, lm-studio, mcp-provider, local-runtime
ExecutionHandoff → V5
ownerfuture-execution-runtime
broker grantbrokergrant:brk-authorized
provider refdeferred
The plan is what the future Execution Runtime (V5) consumes. Nothing executes here: no API is called, no model invoked, no credential held; providerRef is deferred.
Excluded providers (why each was filtered)
enterprise-customenterprise_restricted
enterprise-restricted provider not permitted by preferences
Request inputs
required capabilitiestext
broker requestbrk-authorized
execution intent (M50)—
preferencesmaxCost high · prefer google-gemini
context / at ordinal8,000 tok @ 100