QG310 Router out of step¶
| Type | Bug |
| Severity | High |
| 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 defect of the router's build: the router and its inputs are out of step |
| Gates by default | no, unless the project's quality profile adds it |
Raised when¶
The intent library and the model disagree, the router's rung differs from the library's, or an intent does not resolve to its own label or cannot be separated.
Why it matters¶
The router and the documents it was generated from describe two catalogues.
How to fix it¶
Regenerate the library and the router from one model, at one rung.
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.