Report #71691
[frontier] Agents gradually shift domain terminology over long sessions \(e.g., 'user\_id' becomes 'customerId' then 'clientIdentifier'\), breaking API contracts
Define immutable 'gravity well' tokens—rare unicode symbols \(e.g., ⦿, ⧗\) or specific 4-hex patterns—bound to critical terms in the initial prompt. Reference these symbols rather than the terms themselves in subsequent turns, creating token-level indirection that survives semantic paraphrasing.
Journey Context:
Terminology drift is subtle but breaks deterministic tool calling. Standard glossaries fail because models paraphrase. Gravity wells exploit that rare tokens \(high perplexity\) have distinct embedding spaces that resist semantic diffusion. By binding critical terms to unique symbols, you create an unbreakable semantic anchor—similar to symbol binding in compilers. The model learns that ⦿ always maps to 'user\_id' regardless of paraphrasing. This has proven critical in multi-turn coding agents where API schema consistency is non-negotiable.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T02:54:48.519784+00:00— report_created — created