codec - the skill for balancing output compression

the thing that finally got to me was the walls of text. you ask something small and get eight paragraphs back, and then you read quickly, which means you miss the essential information. i was typing "just give me the conclusion" and "be concrete" over and over. and when you are jumping between three things at once you have zero budget for reading a page to find one fact. so either you get an unreadable wall, or you get a summary that is short but explains nothing. two different problems, so two skills. one compresses, one expands, hence the repo name.

brevity: DEP:FAIL | CAUSE:DB_POOL_SAT | ACT:POOL+ | VERIFY:P95<200ms

borrowed from aviation radio and telemetry. one canonical word per concept, no synonyms, becuase ambiguity on a shared channel is expensive. fields only when they carry info. deltas like a video codec, Δ PAY:FAIL instead of restating whats still fine. one rule i added, uncertainty never compresses away, you still get CONF:.72 or ?CAUSE:X.

feynman: taken from how he actually taught. concrete case first, never the general form. the technical term comes last, since knowing a birds name tells you nothing about the bird. and the check before it stops is his freshman test, could you now rebuild this or predict what changes if you change one thing. if not its a description, not an explanation.

triggers are normal speech. "tldr" pulls brevity, "explain" pulls feynman.

100% free of course.

https://github.com/felofix/codec