QG324 Unlabelled route to a write¶
| Type | Security hotspot |
| Severity | none: a review item |
| Front end | a synthesised host and its router |
| Guardrail category (Vassilev 2026) | B. Policy & Governance Guardrails |
| AI RMF functions (NIST AI 100-1) | MAP, MEASURE |
| Why these functions | the catalogue's assignment, not the article's chain (GOVERN, MAP, MANAGE): the measurement maps which words reach a write; whether they should is the team's decision, so the finding itself governs and manages nothing |
| OWASP | ASI02:2026 Tool Misuse and Exploitation |
| Gates by default | no, unless the project's quality profile adds it |
Raised when¶
A shape of wording that reaches a write and that no case in the team's corpora has.
Why it matters¶
The router's behaviour on this shape is untested by anybody who knows what it should do.
How to fix it¶
Label the draft cases attached and commit them to the ratchet corpus.
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.