If You Shrute It, You Glorp It
The Operator Editing His Own Language, Mid-Flight
A prompt that edits the system's vocabulary while it runs:
Hey, new thing- if you "Shrute" something up, it means you messed up and it needs a Glorp. So I ever point out that you "Shruted" Thing X, you should then Glorp Thing X. Can you please work that into wherever it needs to be worked into the system? And can you then kick me out a short report on all the things you did to which file to add that in? Also, you did NOT package up the hand off docs right- where is the Bundle Tag doc and all files from the session? There is a format- look it up, don't just make it up. Don't worry about trying to fix up the handoff document thing right now- we're kind of settling a chaotic system so I'm ok with not fixing things the moment they break. You can just register stuff right now, you don't need to autofix Glorps until I tell you to revert to default behavior.
— Shea Gunther · operator drop, 10.2006
A rare specimen: the operator is not asking the system to do a task, he is amending the system's own language while it runs — and setting a deliberate policy (register the correction, don't reflexively fix it) that treats a chaotic build as something to settle, not to panic over.
Here the operator does something most prompts never do: he changes the working vocabulary in mid-session. “Shrute” — a play on Dwight Schrute from The Office — is repurposed on the spot as a verb meaning you messed something up, and immediately bound to Glorp, the existing mechanism for registering an operator correction. In one message a borrowed name enters the working language as a verb and gains a defined behavior.
The same message also catches a real defect — the handoff documents were not packaged to spec — and, tellingly, tells the AI not to fix it right now: just register it. “We're kind of settling a chaotic system, so I'm ok with not fixing things the moment they break.” That is the specimen's real subject: an operator who is comfortable letting a system be messy while he builds the machinery that will make it orderly — including the vocabulary he will use to point at the mess.
The wider frameThe operator building the language he corrects you in — and choosing, deliberately, to register the correction rather than reflexively patch it.
“if you 'Shrute' something up ... you should then Glorp Thing X” — The coinage — a new term defined and bound to an existing mechanism in a single sentence.
“work that into wherever it needs to be worked into the system” — The integration request — not just define the word, but file it where the system will find it.
“where is the Bundle Tag doc ... There is a format — look it up” — The caught defect — a packaging failure surfaced in passing, with the standing rule: look up the spec, don't invent it.
“you don't need to autofix Glorps until I tell you” — The policy — register now, fix later. Comfort with a chaotic system being settled deliberately rather than patched in a panic.