The oracle refusal for a route whose agent's role setting does not point at the routed connection still says which model such a route asks for is not yet decided, and its doc comment says the record does not yet decide it. The product thinker ruled on 2026-09-29 (BR1) that such a route is refused, naming the one setting to add, as built in e1c4e38ad and 35100512e, so the refusal is now the decided behaviour and the words not yet decided tell the person a ruling is still coming when none is. The fix is wording only: drop the not-yet-decided clause from the error in internal/core/oracle/resolve.go (take) and the comments in resolve.go and tier.go, keeping the named setting, and adjust any test that pins the old sentence.

The oracle refusal for a route whose agent's role setting does not point at the routed connection still says which model such a route asks for is not yet decided, and its doc comment says the record does not yet decide it. The product thinker ruled on 2026-09-29 (BR1) that such a route is refused, naming the one setting to add, as built in e1c4e38ad and 35100512e, so the refusal is now the decided behaviour and the words not yet decided tell the person a ruling is still coming when none is. The fix is wording only: drop the not-yet-decided clause from the error in internal/core/oracle/resolve.go (take) and the comments in resolve.go and tier.go, keeping the named setting, and adjust any test that pins the old sentence.

Grounds

• pursued: the refusal a person sees for a route whose agent's role does not point at the routed connection names the setting to add and no longer says a ruling is coming; TestResolveRefusesALegTheAgentsRoleDoesNotPointAt would show it wrong by failing on a refusal that names 'not yet decided' or 'undecided', or omits 'a route that names no model is refused'.