Routed is presented in the supplied case as a released local hybrid router for selecting AI-agent skills, attributed to maintainer bshea-1. The maintainer’s HN submission reportedly claims routing in under 20 milliseconds without consuming model tokens, potentially avoiding a model call for skill selection. None of the supplied search snippets directly documents Routed or independently verifies its release, implementation, or performance; they discuss other routing systems, and do not establish that Routed routes between local and cloud models.
Routed’s claimed model-call-free skill selection illustrates Scott’s existing Placement Judgment position and Deterministic agent control plane design, rather than establishing a new architectural claim. The supplied material offers only maintainer testimony—not implementation details, routing-quality evidence, or verified latency—so it does not yet justify changing his routing approach; related radar pages track discovery costs, but not Routed itself.
ip:concept.placement-judgmentdev:concept.deterministic-agent-control-planeradar:concept.agent-skillsradar:mcptoon-tool-discovery-compression
queries asked of Scott's wikis
- agent harness skill discovery and routing
- deterministic dispatch versus LLM skill selection
- routing latency and model-call token costs
- local hybrid retrieval for tool selection
- skill routing accuracy and fallback evaluation
2026-09-09T00:25:43Z
Routed remains a maintainer-announced tool, not a demonstrated routing advantage; this review adds no substantive evidence beyond previously assessed promotion. With no pending evaluation or consequential integration identified, the episode can leave active monitoring without treating its performance claims as disproved.
2026-09-06T23:51:20Z
The live-demo post is more of the same maintainer's amplification (same account, low engagement, no independent testers or benchmarks). Routed remains an unvalidated single-author claim; nothing here changes routing-quality or latency evidence.
2026-09-06T23:26:39Z
evidence attached: reddit.post.1w9a3vj — Post provides a live demo and implementation details for the Routed zero-token skill router, directly supporting the open case.
2026-09-06T17:27:44Z
The two additional posts are same-builder amplification of Routed’s existing announcement, not independent adoption or validation. The tool remains a candidate for evaluation rather than evidence of a practical routing advantage; routing accuracy, realistic CPU latency and end-to-end savings are still untested in the supplied evidence.
2026-09-06T17:22:31Z
evidence attached: reddit.post.1w916v3 — Duplicate coverage of the released Routed skill router supports the existing case but adds no independent validation.
2026-09-06T17:22:31Z
evidence attached: reddit.post.1w90x3i — This is a direct release report for Routed, bearing on whether zero-token local skill routing becomes practical.
2026-09-06T16:24:23Z
The newly attached Reddit post repeats the same builder’s announcement, not an independent user report, so the attachment’s corroboration label overstates the evidence. Routed remains a concrete tool to evaluate rather than a demonstrated routing advantage; realistic routing quality, latency and end-to-end savings remain unvalidated.
2026-09-06T16:22:36Z
evidence attached: reddit.post.1w8zdga — This is direct user-level corroboration of the released Routed artifact and its zero-token local skill-routing approach.
2026-09-06T04:22:33Z
The Reddit builder announcement makes Routed a more concrete implementation to track, but a second platform and different handle do not establish independent corroboration. The release is worth retaining as a control-plane example; routing quality, latency under realistic skill inventories, and practical savings remain unvalidated.
2026-09-06T04:21:31Z
evidence attached: reddit.post.1w8krlv — This Reddit post independently corroborates the released Routed artifact and its zero-token, local skill-routing design.
2026-09-06T03:27:18Z
No substantive new evidence changes the interpretation: Routed remains a maintainer-announced implementation with unvalidated latency and routing quality. The GitHub echo repeats the same claim rather than independently corroborating it, so this remains an example of Scott’s existing control-plane approach, not a reason to change it.
2026-09-06T03:24:47Z
grounded: known/low — Routed’s claimed model-call-free skill selection illustrates Scott’s existing Placement Judgment position and Deterministic agent control plane design, rather t
2026-09-06T03:22:26Z
case created — A linked implementation anchors a bounded routing-performance claim distinct from existing harness cases, though no measurements or usage reports accompany the submission.