4 min readfrom Machine Learning

Competence Gate: gating tool-use on a small model's internal confidence signal instead of its verbalised one — Qwen3.5-4B, open weights [P]

Our take

Introducing Competence Gate, a novel approach to enhancing small language model reliability. This open-source project, built with a 10MB LoRA adapter for Qwen3.5-4B, intelligently governs tool usage based on the model's internal confidence signal, rather than its verbalized output. Early results demonstrate a significant improvement in error detection (d′ of 0.46) and a notable reduction in private query leakage to public search (22% to 10%). Traceable answers and a commitment to saying "I don't know" are core principles.

The recent release of “Competence Gate” by Synthium-jp represents a significant step toward addressing a persistent challenge in the realm of small language models (SLMs): their unreliable self-assessment of confidence. These models, while increasingly capable, often confidently assert answers even when lacking sufficient grounding, a problem exacerbated by their limited parameter count. Synthium-jp's work, detailed in a recent post, introduces a 10MB LoRA adapter that intelligently routes queries based on the model’s internal activation signals, deciding whether to answer directly, search the web, or retrieve from local documents. This approach is particularly timely, given the ongoing exploration of building focused LLMs for specialized tasks, many of which rely on smaller, more efficient models – a trend highlighted in [Is machine learning research worth it for now?] [/post/is-machine-learning-research-worth-it-for-now-d-cmr9j7qzd01enkwjw643t8246]. The core innovation lies not in expanding the model's knowledge base, but in refining its ability to recognize and admit its own limitations, a crucial ingredient for building trustworthy AI systems.

The practical implications of “Competence Gate” are substantial, particularly concerning data privacy and accuracy. The ability to detect and redirect sensitive queries – such as those pertaining to medical records – to local retrieval mechanisms significantly reduces the risk of inadvertently exposing private information to public search engines. Initial results showing a 12% reduction in such leaks underscore the potential impact of this relatively lightweight adaptation. Moreover, the traceability of answers, with citations and confidence bands, fosters greater accountability and allows users to critically evaluate the information provided. While the initial release acknowledges limitations, notably around grounded document QA – a point emphasized by the author’s own testing against external benchmarks, aligning with the critical self-assessment frequently seen in the open-source ML community - the focus on parametric competence, as opposed to evidential grounding, is a valuable distinction. This distinction is echoed in the challenges encountered when building and curating specialized datasets, as exemplified by [I built an open, from-scratch MT pipeline + parallel corpus for Tunisian Darija (Arabizi) early baseline, and I'm growing it into a curated community corpus] [/post/i-built-an-open-from-scratch-mt-pipeline-parallel-corpus-for-cmr9j82rc01ffkwjwpv4r0h2z].

What makes this work particularly compelling is its accessibility and extensibility. The adapter's small size (10MB) allows it to be readily integrated into existing SLMs, and the methodology is designed to be adaptable across different model architectures. The author's explicit encouragement of critique and the open-source nature of the release foster a collaborative environment that can accelerate its refinement and broaden its applicability. The decision to use GGUF builds for both MLX and llama.cpp/Ollama further expands the accessibility of the tool, aligning with the broader movement toward democratizing access to powerful AI capabilities. This is a far cry from the often-hyped pronouncements of “revolutionary” breakthroughs; instead, it’s a pragmatic and incremental improvement that addresses a tangible pain point in a clear and actionable way. This contrasts starkly with the marketing surrounding some larger models, where the underlying methodological rigor is often obscured.

Ultimately, “Competence Gate” highlights a crucial shift in focus within the AI space: from simply increasing model size and capability to improving the reliability and trustworthiness of existing models. By prioritizing accurate self-assessment and responsible tool use, Synthium-jp’s work paves the way for more dependable and user-centric AI applications, especially within resource-constrained environments. As we continue to explore the potential of SLMs for a wide range of tasks, the ability to confidently discern when a model *doesn’t* know is likely to become as important as its ability to answer questions. Will this approach spark a broader movement toward building "honest" AI systems, prioritizing transparency and accountability over sheer predictive power?

I made a 10MB LoRA adapter for Qwen3.5-4B plus a small orchestration layer. It decides, per query, whether to answer directly, search the web, or retrieve from your own local documents and it refuses to make things up when it can't verify an answer.

It runs locally (Apple Silicon / MLX, with a GGUF build for llama.cpp/Ollama).

Basically small instruct models are poor at telling users how confident they really are. They can't verbalise it and tend to say they are confident for everyhting. In my past research I tested seven 3-9b models and they all hit a confidence ceiling. But the information is there in the internal activations. The adapter reads the internal signal directly and gates tool use on it.

The main elements are that:

- it catches its own errors better than the base model's tool calling (d′ improvement of 0.46 (95% CI [0.01, 0.89])). Of the cases the gate flagged that the base model didn't, 87% were genuinely wrong answers.

- it is less likely to leak your private queries to public search. A two-signal version routes personal information related questions such as "what did my discharge summary say" to a local retriever instead of a websearch. It cut the rate of private questions sent to public search from 22% to 10% (reduction 0.12, 95% CI [0.02, 0.22]). This is useful for those who are using the LLM for confidential docs.

- every answer is traceable. When it retrieves, it cites the specific passage (report.md ¶2), verifies the answer is actually in that passage, and shows a confidence band. Worst case, it says "I couldn't verify that". It is built to say "I don't know," instead of lie.

limitations:

- Privacy result is n=60; the retrieval/competence dissociation is n=126 hand-authored items. Screened and CI'd, but small.

- GGUF reproduces the MLX gate's decisions at --lora-scaled ...:8 (found by sweep — scale 1 does nothing; effective scale ≈ the training scale). Agreement 0.83 on a 24-item probe; disagreements are all conservative-direction (GGUF answers a couple of borderline items MLX would look up), and knowns never false-fire. Faithful on the safety-critical directions, marginally more conservative at the margin.

- Serve-time confidence is coarse (grounded / declined / answered) — the distilled gate reads nothing at inference, so finer bands need probe access (offline).

- Inherits Qwen3.5-4B's knowledge and biases. The gate governs when to trust the model, not what it knows.

The approach isn't Qwen-specific — I started on SmolLM3-3B, and it should extend to other models and larger sizes.

Repo (weights + code + model card): https://huggingface.co/synthiumjp/competence-gate-qwen3.5-4b

Apache-2.0. It's an open research release. I hope people might find some use for it. Methodology and papers are cited in the model card. Genuinely interested in critique, it's screened work, so if there are any issues it be great to know.

**** Update ***\*

I ran the gate against external benchmarks it hadn't been tested on, and one use case did not survive. The gate does not improve grounded document QA — answering faithfully from a provided passage and abstaining when the passage doesn't support an answer. On SQuAD 2.0 unanswerables, fabrication was actually higher with the gate than without it.

The reason is a example of construct specificity. "Knowing when to defer" is not one capability. There are at least two distinct signals hiding inside it:

- Parametric competence: do I know this from my own weights? The gate reads this. It's what the probe was validated against.

- Evidential grounding: is this answer supported by the passage in front of me? A different question, from a different information source.

A probe validated for one carries no usable signal for the other. A parametric-competence signal applied to an evidential-grounding task doesn't just fail to help, it actually interferes by pushing toward answering and suppressing the base model's (Qwen's) own abstention. The base model already handles the easy case (0% fabrication when the passage plainly lacks the answer). The hard case (adversarial unanswerables) needs purpose-built grounded-abstention training, not a post-hoc firewall.

The release is scoped to what's validated: parametric tool-call routing and privacy-aware retrieval routing. The "refuses to fabricate about documents" framing in the original post above is the part that doesn't hold.

submitted by /u/Synthium-
[link] [comments]

Read on the original site

Open the publisher's page for the full experience

View original article