Siu's Op#52 opens its discussion of loftiness with a small four-row translation table. The table is technically a parenthetical example. It is also one of the most operationally readable artifacts in the entire book.
"Instead of frankly stating: 'He's a man of limited ideas,' the letter says: 'He's an excellent team worker.'
Instead of frankly stating: 'He's a yes-man,' the letter says: 'He's a staunch supporter of his superiors.'
Instead of frankly stating: 'He's a big mouth,' the letter says: 'He's a vigorous speaker who really sells his ideas.'
Instead of frankly stating: 'He's afraid to make decisions on his own,' the letter says: 'He's one of our most active management committee members.'"1
Read the table once, fast. The euphemisms are not lies. Excellent team worker is technically true of a man of limited ideas — limited ideas mean he never proposes the unconventional move that would disrupt the team. Staunch supporter of his superiors is technically true of the yes-man. Vigorous speaker is technically true of the big mouth. Active management committee member is technically true of the indecisive person who hides in committees.
Each translation is cover — language that elevates a fact about the candidate to a higher-order frame in which the fact reads positively. The cover is the substance of the operation. The reader who knows the code reads the cover backwards to recover the original fact. The reader who does not know the code reads the cover forwards and sees a positive recommendation. Both readings happen against the same words.
First wire (obvious): This is bureaucratic doublespeak. People at work say one thing and mean another to avoid causing offense. Standard professional politeness.
Second wire (deeper): The structure is more interesting than politeness. Politeness softens a fact while keeping the fact recoverable. He has limited ideas, but he's a hard worker is polite. He's an excellent team worker — with no qualifying clause — is not polite. It is cover. The fact has been suppressed entirely from the surface text. Recovery requires either possession of the code or comparison with the candidate's actual performance. The euphemism table is therefore not a politeness operation. It is a parallel-language operation: insiders speak Code English, outsiders speak Plain English, and the same words map to opposite meanings depending on which language the reader is fluent in.
Third wire (uncomfortable): Most professional environments run partly or entirely on Code English without the participants noticing the bilingualism. The discomfort: the reader who has spent decades in such environments is no longer reliably able to write Plain English about colleagues, even when the situation calls for it. Code English has become the default. The reader who tries to write a frank performance assessment finds themselves reaching for the polite translation automatically; the candidate-of-limited-ideas comes out as excellent team worker before the writer notices the substitution. The bilingualism erodes from one direction. Code English drives out Plain English. The institution that runs on the cover language eventually loses access to the underlying language entirely, which is the moment when honest performance reviews become structurally impossible — not because the writers won't write them but because the writers can no longer find the words.
Same domain folder first. Lofty Cover / Natural Harmony — the dedicated Siu Op#52 page; the table is the canonical example. This spark is the operational micro-instance of the page's mechanism.
Manufactured Legitimacy — Siu Op#51. The Lofty Cover mechanism the table demonstrates is the small-scale linguistic version of the same operation that produces manufactured legitimacy at institutional scale. The Honolulu gang trick (small boy as bait engineering the rescue-pretext) and the letter-of-recommendation euphemism are the same move in different costumes. Both elevate a fact (gang wants to fight; candidate has limited ideas) to a higher-order frame in which the fact reads acceptably (gang is rescuing a kid; candidate is a team worker). Both require the audience to read the cover forward, not backward.
Cross-domain reach: Depersonalization as Power Mechanism — Siu Op#77. Code English depersonalizes. Excellent team worker describes a function, not a person. Active management committee member describes a role, not a behavior. The euphemisms work because they substitute role-categories for person-categories. The pronoun shift Siu identifies in Op#77 (we are persons; they are impersons) operates here at the lexical level — the candidate becomes a function of the institutional role, and the institutional role can be honestly characterized in cover language without anyone lying.
Essay seed: "How institutions stop being able to say what they mean — bilingual erosion in professional language." The angle: most discussions of bureaucratic doublespeak treat it as a politeness phenomenon or a conspiracy of euphemism. The Vault-Pith reading is structural — Code English drives out Plain English over institutional time, and the loss of Plain English is the failure mode that produces unaccountable bureaucracies. The piece would compare three or four institutional contexts (academia, the military, modern HR, finance) and ask which ones have managed to preserve a working Plain English alongside the Code English, and which have lost it entirely.
Concept page candidate: "Code-English / Plain-English Bilingualism — when professional language becomes a parallel-translation system." The page would map the structural mechanism (cover language elevating facts to higher-order frames in which the facts read acceptably), the failure mode (Plain English erosion), and the implications for accountability. The handshake to behavioral-mechanics is direct. The handshake to creative practice is also relevant — writers who produce documentary nonfiction often face the inverse problem (translating Code English back to Plain English), and the experienced ones develop specific tools for the back-translation.
Practical artifact (this is the unusual case for a spark): the table itself is a tool. A reader doing performance reviews could keep the four-row table on their desk and use it to check their own writing. If their draft contains the right-column language, they can ask: which left-column fact is being covered? The forced back-translation prevents the unconscious slip into Code English. Filing the table as an open practical artifact in the vault is itself worth considering.
[ ] A second source touches this independently — would need either a corpus-linguistics analysis of letter-of-recommendation language across decades, or a comparable translation-table from another professional domain (military performance evaluations, academic tenure letters, etc.) [x] Has survived two sessions without weakening [x] The Live Wire second framing holds — the parallel-language reading is structurally what makes the table generative beyond a one-off joke [x] Has a falsifiable core claim — the bilingual erosion claim is empirically testable through historical analysis of professional writing across an institution that has been observed for several decades