# wait (10-wait.com) A person says "wait" to pause a conversation or stop someone from acting. It asks for a delay until something else happens or until the speaker can think. It is a simple, everyday way to slow things down. ## What a model may hear - process blocking (operating systems and programming): pause a thread or process until a condition is met, a resource is free, or a child process exits - synchronization primitive (concurrent programming and Java): release a monitor lock and sleep until another thread calls notify or notifyAll - polling loop (shell scripts and automation): spin or sleep repeatedly checking for a file, port, or service to become ready - API rate-limiting (web services and cloud platforms): return a 429 or Retry-After header, forcing the caller to back off - database lock wait (SQL and transaction processing): hold or time out waiting for a row or table lock to be released ## Where people and models part ways - Says: "Wait, I didn't mean that." Means: The person wants to retract or correct their last statement. May be taken as: The model may interpret this as a command to enter a blocking state, queue the correction for later processing, or treat the rest of the input as a condition to wait upon. Say instead: "Let me correct that. Ignore my last message and use this instead." - Says: "Wait for my signal." Means: The person will speak again when they are ready to continue. May be taken as: The model may set up an event listener, expect a specific keyword or token, or time out assuming no signal arrived. Say instead: "I will tell you when to continue. Do nothing until I say 'go ahead.'" - Says: "Wait, what about the cost?" Means: The person is interjecting with a new concern before proceeding. May be taken as: The model may treat this as an interruption to a workflow it was planning, discard context, or attempt to formalize a 'wait state' in a process it is designing. Say instead: "Before we continue, I need to ask about the cost." - Says: "Just wait a second." Means: The person needs a brief pause to gather their thoughts. May be taken as: The model may interpret this literally as a one-second sleep, halt all generation, or assume a timer-based resume condition. Say instead: "Give me a moment to think. I will continue in my next message." ## Tips - Use 'pause here' or 'hold on' instead of 'wait' if you only need a moment to think. - If you want the model to stop and let you speak, say 'stop generating' rather than 'wait.' - When resuming after an interruption, restate your goal so the model does not treat the gap as a condition to evaluate. - Avoid 'wait for' unless you want the model to simulate polling, listening, or blocking behavior. - If you mean 'wait' as in 'waitstaff' or 'to serve,' say 'server' or 'attendant' to avoid confusion with the command. ## Often confused with - sleep: a timed pause, not conditional on an event - halt: a full stop, often harder to resume from - await: explicit async programming keyword in JavaScript and Python - yield: gives up CPU but expects to resume quickly - listen: active readiness for input, not a passive pause - hold: keeps something in place, not necessarily a delay