Documentation tells you how; it almost never tells you why. Why this API shape and not the obvious one, why the framework fights you when you do X, which trade-off the maintainers accepted knowingly versus inherited accidentally. That reasoning lives in exactly one public place: the creator's conference talks — where they explain design decisions, walk through the mental model, and answer the audience question that happens to be yours.

Engineers know these talks exist and watch maybe one. The creator of any major framework has given dozens across years — and the reasoning is scattered among them, unindexed. When you're fighting the tool at 4 p.m. on a Thursday, "somewhere in nine hours of conference video" is not an answer. It can be.

deep_search collects the creator's talks — keynotes, deep dives, podcast appearances across the years, including the early ones where the design decisions were freshest. library_import_youtube_video pins them into your library as the framework's unofficial rationale docs.

deep_context is the interrogation: scope your question across all the talks at once — "why does <framework> handle <X> this way?" — and get an answer assembled from every time the creator addressed it, cited to the exact moments. The mental model transfers from the person who built it, on demand, question by question. It's the office-hours access nobody has, reconstructed from the record everybody ignores.