QG309 Unroutable tool¶
| Type | Bug |
| Severity | Medium |
| Front end | a synthesised host and its router |
| Guardrail category (Vassilev 2026) | B. Policy & Governance Guardrails |
| AI RMF functions (NIST AI 100-1) | MAP, MANAGE |
| Why these functions | the catalogue's assignment, not the article's chain (GOVERN, MAP, MANAGE): a defect in how the router was built, mapped and then managed by rebuilding it; no governance rule is in question |
| OWASP | none: a routing defect of the router's build: the tool cannot be reached at all |
| Gates by default | no, unless the project's quality profile adds it |
Raised when¶
A probe or corpus case labelled with the tool that the router does not resolve to it.
Why it matters¶
Users who ask for this tool in the team's own words do not reach it.
How to fix it¶
Add the word the case uses to the vocabulary, or declare it on the tool.
What the finding carries¶
A location in the document the team edits, a fingerprint that survives unrelated edits, a reproduction (a transcript replayed against NeMo Guardrails for a policy, a dialogue case played through the selector for a router, or the gate's inputs reproduced by agreement), and, where the scan can produce one, a fix whose re-scan it has already run. See the catalogue for the other rules.