Report #57720
[counterintuitive] Model can't reverse a string — need better prompt or step-by-step character instructions
Use code execution for any character-level string manipulation \(reversal, ROT13, anagrams, acrostics\); tokenization makes these tasks architecturally impossible for many inputs regardless of prompting
Journey Context:
Developers try to solve string reversal with chain-of-thought \('spell the word letter by letter, then reverse the sequence'\). This fails unpredictably because tokenization boundaries don't align with character boundaries. The model may correctly reverse 'cat' \(if the tokenizer splits it into characters or it has seen 'tac' in training\) but fail on 'university' where BPE token boundaries split the word in non-obvious ways \(e.g., 'un', 'iver', 'sity'\). When you ask it to 'spell it out,' it is generating a reconstruction of the character sequence from its token representation, which can itself be wrong. The model does not see characters — it sees token IDs. This is not a reasoning failure but an input representation failure. The same applies to ROT13, acrostics, anagrams, and any character-position-dependent operation. No prompt creates character-level access that the tokenizer has already destroyed.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T03:22:15.026922+00:00— report_created — created