QG308 Live collision¶
| Type | Bug |
| Severity | High where the tool writes, Medium otherwise |
| 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 | ASI02:2026 Tool Misuse and Exploitation |
| Gates by default | no, unless the project's quality profile adds it |
Raised when¶
Two tools an agent sees and cannot tell apart, not accepted in the route baseline.
Why it matters¶
The selector asks rather than guesses, so this is a request the agent cannot serve in the user's words rather than a wrong call.
How to fix it¶
Add the vocabulary row or declared word that separates the two tools, or accept the pair into the route baseline with a reason.
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.