local-first · v0.1

Reasoning selection

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.

selectedanthropic-claudeblockfailovercost highbinding: false#4db378bc
broker grant:brokergrant:brk-authorizedbroker:brk-authorizedcontext:8,000 tok

Routing decision (fail-closed)

provider_selectedroute
selected "anthropic-claude" (priority 1, cost high); 5 fallback(s)
Failover chain
anthropic-claude → openai-gpt → google-gemini → nvidia-nim → deepseek → ollama

Selection & handoff (V5 readiness only)

Selected provider
provideranthropic-claude
matched capabilitiestext, reasoning
context limit200000
fallbacksopenai-gpt, google-gemini, nvidia-nim, deepseek, ollama
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)

lm-studiocapability_unmet
missing capabilities: reasoning
mcp-providercapability_unmet
missing capabilities: reasoning
local-runtimecapability_unmet
missing capabilities: reasoning
enterprise-customenterprise_restricted
enterprise-restricted provider not permitted by preferences

Request inputs

required capabilitiestext, reasoning
broker requestbrk-authorized
execution intent (M50)
preferencesmaxCost high
context / at ordinal8,000 tok @ 100