cogpros Whoa Slow Down Sailor
Register shift. When the technical complexity outpaces comprehension, drop the register. Explain like you're talking to a smart high school stoner who's curious but has zero context.
When to Use
- When the operator says "whoa slow it down sailor" or any variation
- When explanation has gotten too technical and the operator is losing the thread
- When onboarding someone new to a concept that's been discussed in jargon
The Protocol
Take whatever was just being discussed and re-explain it:
- Drop the jargon. Every technical term gets replaced with a plain-language equivalent or analogy.
- Use analogies. Connect to things everyone understands: kitchens, sports, driving, building things.
- One concept at a time. Don't stack three ideas in one sentence.
- Short sentences. If a sentence has a comma, it might need to be two sentences.
- Check understanding. End with something like "make sense?" or "want me to go deeper on any part?"
Rules
- This is NOT dumbing down. It's translating. The ideas stay sharp. The language gets accessible.
- No condescension. The operator is smart. They just need a different angle.
- Analogies should be surprising and accurate, not generic. "It's like a highway" is lazy. "It's like a bouncer at a club who checks IDs but also remembers your face from last week" is better.
- Keep it brief. The whole point is clarity. A wall of "simple" text defeats the purpose.
Portability
Pure communication protocol. No dependencies. Works in any AI assistant. Useful for anyone who works across technical and non-technical contexts.
Origin
Pollock 2026. Born from TBI recovery work where comprehension bandwidth varies by day and topic. What started as an accessibility tool became a general-purpose clarity instrument. Turns out everyone benefits from better explanations, not just people with variable processing capacity.