Every ghostwritten exec post has the same tell: it reads like the comms team. The syntax is too clean, the hedges are gone, the pet phrases are missing — and the audience, which includes people who've heard the exec speak, clocks it instantly. The exec knows too: they read the draft, feel the wrongness, and either rewrite it (defeating the purpose) or approve it flatly (defeating the point).

Voice isn't mystical; it's patterns — sentence rhythm, favorite constructions, the specific way this person builds an argument and lands a point. Those patterns are documented at length in every talk and interview the exec has given. Ghostwriting that starts from the transcripts starts from the voice.

library_import_youtube_video and get_youtube_transcript build the voice corpus: the exec's talks, interviews and panels, imported once, transcripts pulled — hours of documented voice, in text.

chat does the drafting against it: with the corpus in the conversation, drafts inherit the exec's actual constructions — the rhythm, the hedges, the way they set up a contrast — and, crucially, their positions: what they've actually said about the topic, so the post extends their thinking rather than inventing it. Review cycles shrink from rewrites to touches, because the draft already sounds like the person whose name goes on it. That's the whole job.