# X_ERROR_CODE_UNRESOLVED

## Means

an error code is written as a name this repository cannot resolve

## Typical cause

the `errors` step read a `code:` whose value is an identifier, and no module-scope `const` in that same file gives it a value — an import, a local, an enum member. Every reader of the code set is then blind to whatever code it holds: no row in `framework.manifest.json`, no row demanded on this page, no entry for `bun run gate-codes`, no `x errors explain` answer. Silent and permissive, so the DRYer the author the less the gate saw (#277). A `const NAME = 'X_…'` in the SAME file is resolved and is not a finding; a table read (`SEO_ERROR_CODES.metaMissing`) is not judged, because the registry it reads from declares those literals itself

## Fix

the `fix` names the offending `<file>:<line>` — write the `X_*` code as a string literal there, or declare it as a module-scope const in that same file

[CLI and verify](/error-codes#cli-and-verify)