QG311 Unshippable synthesis¶
| 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 synthesis cannot be shipped as written |
| Gates by default | yes: a new finding under it fails the default quality gate |
Raised when¶
A refusal the synthesis collected, located on its tool, agent or domain.
Why it matters¶
The rulebook cannot be generated as the inputs stand. The scan keeps going without the refused entity so the rest is still decided, and lists every refusal at once.
How to fix it¶
Fix the input at the location named, under the refusal's slug.
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.