Keep literal evidence separate from explanation
Synthetic error text is exactly “E_FILTER: Column B absent”. The support case stores that literal string and a separate natural Chinese explanation. Replacing the identifier with E_FILTER_ZH or changing B to a guessed Chinese field name alters the evidence. The explanation can describe the reported missing B column without asserting a verified cause or promising a fix. No actual software uses this invented error in the example.
| Part | Stored example | Purpose | Rule |
|---|---|---|---|
| Literal error | E_FILTER: Column B absent | Exact reported evidence | Keep unchanged |
| Chinese explanation | The export reports a missing B column. | Explain in the reader’s language | No guessed cause |
| Changed identifier | E_FILTER_ZH | Not the reported identifier | Do not substitute |
Provide explanation beside the original evidence
- Capture exact error text
- Keep its identifiers unchanged
- Write a local explanation
- Check that meaning and evidence agree
If the original text is unreadable, ask for a clearer record; do not invent a plausible error code.
Which identifier should staff use to compare this reported error?
Show the worked answer
E_FILTER. E_FILTER_ZH is invented and must not replace it. Keep “Column B absent” as part of the original message.
Retain the exact reported string for comparison. Revise the explanation independently when needed without replacing the original identifiers.