experience-and-transmissionlisted

# Experience and Transmission **Problem shape:** correctness is not the bottleneck — arrival is. The system passes its tests and fails its user, the documentation exists and is not read, the code runs and cannot be maintained, or the thing being studied changes because the studier is part of it. The deliverable is comprehension and use, measured on the receiving end rather than asserted on the producing end. ## Relevant geniuses | Agent | Use when | |---|---| | [jobs](../../agents/genius/jobs.md) | the product "works" per component metrics but the integrated experience is broken — treat the whole experience as the spec, hunt the seams, edit ruthlessly rather than add | | [vygotsky](../../agents/genius/vygotsky.md) | onboarding is too slow or too overwhelming, or documentation exists and nobody reads it — locate the zone of proximal development, scaffold inside it, and plan the fading; diagnose the misconception rather than repeating the explanation | | [varela](../../agents/genius/varela.md) | the observer cannot be separated from the system studied (UX research where the experience *is* the product, dogfooding, introspective debugging) — run trained first-person observation and third-person measurement concurrently and report their mutual constraints | | [knuth](../../agents/genius/knuth.md) | the program is correct and unreadable — literate programming, writing for the human reader first; and building the tool before using it when no adequate one exists. **Entry point is