Aakash Gupta Proposes ASD-STE100 as Anti-Slop Prompt for LLMs
Aakash Gupta explains the origins of ASD-STE100, a controlled aerospace maintenance language with about 900 approved words, and argues it can reduce hedging and fluff when used as a prompt for LLMs. The post responds to a Karpathy suggestion to have models write in this spec.
Original post · 2 min read
Karpathy is telling people to ask their LLM to write in ASD-STE100, a controlled language built for aircraft maintenance manuals. I went down the rabbit hole on where this spec comes from, and the backstory makes the hack even better.
Back in the late 1970s, European airlines were handing English manuals to mechanics around the world who mostly didn't speak English as a first language. One ambiguous sentence in a fuel line procedure can get people killed. So the industry built a version of English where ambiguity is banned at the dictionary level.
The spec allows roughly 900 approved words. Each word gets one meaning and one part of speech. "Close" can only be a verb, because "close the door" and "the close door" can't be allowed to coexist in a repair manual. "Follow" only means to come after. If you want obey, you write obey.
Procedural sentences max out at 20 words. One instruction per sentence. Active voice only. Around 1,200 common words are explicitly banned, each with a mandated replacement. You don't "commence pumping." You start the pump.
English has about 170,000 words in current use. Aviation decided mechanics get 900, and planes became safer to maintain because of it.
Now flip it to LLMs. Models hedge and synonym-cycle because the training data rewards sounding fluent. STE is 40 years of accumulated rules for stripping exactly that out, written by people whose readers would die if a sentence could be read two ways. It might be the strongest anti-slop prompt in existence, and it's a free PDF.
Andrej Karpathy @karpathyWe'll be spending a lot more time trying to understand the outputs of language models. A few thoughts, tips & tricks:
Writing. Something I've had success with: Ask your LLM to explain something in ASD-STE100, it's a controlled language specification originally developed for aerospace maintenance documentation. LLMs well-versed in this language and it comes with heavy constraints on clean writing style that I often find a lot more readable. Sometimes I've tried to soften it a bit e.g. ask for "80% of the way to ASD-STE100" because the spec is quite stringent. But even better:
Diagrams / image…

