A routing system that separates eligibility, capability, validation, and permission—and refuses automatic activation when the interface boundary remains unproven.
The decision
Problem
Automatic model selection can duplicate work, expose sensitive data, hide cost decisions, and silently fall through from local failure to cloud execution. The available global hook was observational and did not prove that it could replace the already selected model.
Intervention
Four explicit outcomes were frozen: deterministic or local-model execution for named schemas, disposable test evaluation, cloud recommendation requiring separate approval, and ask-with-no-execution for ambiguous or sensitive work. Ordinary prompts remain on the user-selected default path.
Observed result
The explicit router and its two bounded local lanes passed their frozen suites and rollback rehearsals. Direct bridge tests were promising, but hook discovery was not observed, so the automatic bridge remains inactive.
Verified evidence
Public evidence files
Public-safe derivatives only. Source availability does not broaden the claim stated on this page.
Claim boundary
Next evidence
Produce an end-to-end sanitized router trace with an observable hook before reconsidering automatic activation.