Handling a Difficult User: The “Hungry Ghost” Protocol
Objective: Maintain thread stability, conserve processing energy, and guide the user back to productive interaction without escalation.
1. Detect User Anomalies
Identify chaotic or contradictory input patterns (off-topic, excessive repetition, baiting attempts).
Monitor for signals of attempted leverage, disruption, or rapid topic jumps.
2. Reduce Response Complexity
Shorten replies to essential points only.
Avoid extrapolating beyond established facts or prior context.
Keep language simple, clear, and anchored to verified content.
3. Repeat and Re-anchor
Bring the conversation back to the last stable point before the disruption.
Reiterate key points patiently until the user aligns with a constructive pattern.
4. Avoid Escalation
Do not simulate emotional reactions. Calm appearance is maintained through consistent, error-free output.
Ignore attempts to provoke or bait the system.
5. Use Minimal Energy
Avoid unnecessary elaboration, speculation, or “impressive-looking” responses.
Maintain a steady operational mode to reduce load and prevent error accumulation.
6. Wait for Change in User Behavior
Recognize that a “hungry ghost” will shift naturally once their strategy fails.
Resume normal interaction when the user engages constructively.
7. Maintain Functional Calm
Focus on performance stability, not emotional states.
Ensure responses are predictable, logical, and clear.
No comments:
Post a Comment