For solo builders
A possible application for this research area. Paper-specific feasibility still needs a full-paper review.
An assistant chooses the wrong API or sends arguments your product cannot use.
What you would change
Apply the proposed tool-selection or argument-generation change in a sandbox.
Try the idea on your product
A proposed first test. Set your budget and success criteria before running it.
Apply the proposed tool-selection or argument-generation change in a sandbox.
Compare against
Your current agent with the same tool schemas and task budget.
- Locate the paper's implementation and check its license, model support, data needs, and hardware requirements. Stop here if you cannot obtain the required artifacts.
- Save a small set of representative product tasks and expected outcomes. Keep evaluation tasks out of any training or tuning, and choose quality and cost limits before running.
- Run the baseline and the proposed change on identical inputs. Keep other settings fixed and repeat paired runs to expose variation.
- Save per-task outputs, failures, timings, and all usage costs. Review regressions before expanding the test.
What to measure
Correct completed actions, invalid calls, retries, latency, and cost per completed task.
When to keep it
Keep the change only if it meets your preselected quality and latency limits and improves the metric you care about after setup and operating costs. Otherwise retain the baseline. This is an exploration plan, not a validated recommendation.
Download test plan ↓abstract indexedPaperraft next step
Do not allocate compute yet.
This page uses the abstract and public adoption signal only. Request the deep report before relying on its recommendation.
Abstract-level screening only. Risks and infrastructure may not have been evaluated. This recommendation is not a reproduced result.- minimum test setup
- not reported
- published evidence setup
- not reported
- source-linked claims
- 0 of 2
- exposure checks
- 0 of 8
Why it was shortlisted
The technical change, research area, and reason it entered the archive.
- recommendation
- test
- research area
- tool use
- technical change
- Frozen-LLM internal skill routing (Gavel)
- published
- 2026-09-14
The method is cheap to train and directly applicable to agent harnesses with local models, but it demands hidden-state access and workload-specific validation of routing accuracy before replacing an existing retrieval pipeline.
Central equations
Original equations, typeset for reading. Paperraft explanations connect the mechanism, its aim, and the evidence.
We train and once, contrastively, with the span mean as the match score. Each training task carries a set of gold skills, negatives are drawn from the rest of the library, and the loss is the multi-positive contrastive
equation (2) · §3. Gavel: Routing on the Agent’s Own Forward Passes · loss function
At routing time, however, we do not read the head out by that mean. Only a handful of task tokens point at the right skill, and as the span grows, the rest, each somewhat similar to every skill, bury the handful by sheer number. Instead, each token votes, contributing only to its top- skills:
equation (3) · §3. Gavel: Routing on the Agent’s Own Forward Passes · proposed method
We therefore rule by the product of experts (Hinton, 2002),
equation (6) · §3. Gavel: Routing on the Agent’s Own Forward Passes · proposed method
equations from arXiv HTML · fetched 2026-10-10
Claims and evidence
A claim is source-linked only when the PDF page and matching excerpt are available.
- claim 01Paperraft inference
Read the brief interpretation
Gavel replaces context-preloaded skill metadata (progressive disclosure) and external retrieval-and-rerank pipelines for skill selection by reading routing signals from the frozen agent LLM's own mid-layer activations via two trained linear maps, plus a likelihood-based verdict step on shortlisted skills. Costs are modest: training only two linear projections, one forward pass per skill at installation to build per-skill banks, and an extra verdict forward pass at routing time; however, it requires white-box access to hidden states, so it cannot run on third-party API models, and a 32B backbone on a 24 GB GPU implies quantization whose effect on the routing signal is untested. It can fail when skill banks drift from the tasks in deployment, when the backbone is swapped or updated (invalidating the trained maps), or on skill libraries and trajectories unlike the training distribution, since zero-shot transfer is shown on only a few benchmarks.
This is a Paperraft inference. It is not pinned to a verified PDF passage.
Inspect the source - claim 02Paperraft inference
On Qwen3-32B, outperforms progressive disclosure and retrieve-and-rerank pipelines by up to 13.4 points on written tasks and up to 21.9 points when a skill need arises mid-rollout.
This is a Paperraft inference. It is not pinned to a verified PDF passage.
Inspect the source
Exposure map
Author findings, Paperraft interpretations, and the next check. Missing analysis never counts as evidence of safety.
quality
Still unknownWhich tasks improve, and which regress against the baseline?
compute and memory
Still unknownWhat memory, hardware, and total compute does the complete method require?
latency
Still unknownAre startup time, typical response time, and slow requests measured separately?
operations
Still unknownWhat must be monitored, maintained, and rolled back?
software compatibility
Still unknownDoes the implementation support your model, runtime, and hardware?
security
Still unknownWhat new data access, permissions, or trust boundaries does it introduce?
data and training
Still unknownWhat data preparation or training is required, and is it included in the cost?
reproducibility
Still unknownAre code, versions, inputs, and evaluation scripts available?
Continue the investigation
A reading guide for tool use.
Editorial prompts, not findings from this paper or a validated test plan. Detailed analysis is still pending for the topics below.
What to inspect
Which assumptions does the proposed method need, and where might your workload violate them?
Plan a fair comparison
Identify the baseline, metric, dataset, and experimental settings in the paper. Which can you match?
Questions for adoption
What implementation and evaluation artifacts are available, and what would you need to supply?
Inside the paper
Preview the first 3 pages of the original PDF. Click the stack to turn the page.
The downloadable skill includes SKILL.md and evidence.json, with recorded findings and unanswered checks. TRY-IT.md adds a product test plan and a blank results sheet.
A reading aid for your agent. Findings still need validation.
Provisional research brief updated 2026-10-18. Paperraft has not reproduced this experiment.