Compression as expertise: a summary of problems

Collecting the issues with the "language is compression / expertise is encoding" framework in one place for reference.

Gatekeeping. Compressed terminology functions as an entrance barrier. Acquisition requires time served, not demonstrated understanding. Knowledge leaves when people leave. The term "portable expertise" is used. The expertise is not portable. It is not stored anywhere.

Opacity. No external test distinguishes meaningful compression from empty jargon. The mechanism is identical. Frameworks that treat all domain language as "compression" cannot account for this. They provide theoretical cover for obfuscation.

Fragmentation. Independent compression produces independent codebooks. Teams working on the same systems develop incompatible terminology. Local efficiency increases. Cross-team communication degrades. Net effect is negative at scale.

Rigidity. Terminology calcifies. Initial shorthand becomes mandatory vocabulary. The encoding constrains which thoughts are expressible. Concepts that don't fit the existing vocabulary become difficult to articulate and are eventually dropped.

Framing. The terminology of the framework itself is non-neutral. "Emergent" carries positive connotation. "Specified" carries negative connotation. This is a rhetorical choice presented as a descriptive one. Frameworks that cannot be described in neutral terms should be treated with suspicion.

These are structural properties, not edge cases. Any complete account of compression-as-expertise must address them. I have not seen one that does.