Reach, authority, and promotional are not three hooks for the same script. What distinguishes them is the closing, and a video that tries to be all three at once gets the least reach.

Repo for domain of the flow /promoavatar3 of the inemaccbot. The mechanism is the same as promoavatar — the bot writes and STOPS, you generate the avatars, /aprovar unlocks the rest. The difference is what comes out of the text phase.
The 12 audiences × 3 types = 36 targets, written <publico>-<tipo>: jovens-alc, mulheres-pro, 40mais-aut…
This flow is C#; o promoavatar é A# e o promoclub é P#. The bot rejects references with a mismatched prefix.
The three types for an audience share its channel and trigger — they end up in the same livesN. Recommended order: reach → authority → promotional.
What separates the three is the ending. The -alc there's no commercial CTA at all (spoken or in the reel), the -aut gives the brand a light touch, the -pro converts.
25–40s. Stop the scroll and get shared. The audience comments and shares. CTA: comment / share — never commercial.
35–60s. Teach something concrete and be saved. The audience saves and follows. CTA: save / follow / try.
30–45s. Connect pain to a solution. The audience clicks. One CTA, for inema.club.
That’s why position matters more here than in the promoavatar: without a position on the table, the three types collapse into one — the same balanced summary in three packages, and the -alc becomes impossible, because there’s no such thing as a “contrary opinion” without someone taking a side. Once the position is defined, the three separate: the -alc defends, the -aut explains the mechanics that support it, the -pro turns it into a practical consequence.
The text phase runs once for the entire flow; download and reel run per target.
One file per target in textos/C<N>/<alvo>.md, one more resumo-estrategico.md that says which position was landed on. The bot sends the ### FALA each one in the chat and STOP.
In HeyGen, find the video whose name is exactly C<N>-<alvo>-v1 and downloads the MP4 — the version with burned-in captions when the studio recorded with them, clean captions when it didn't.
Builds the 9:16 reel and delivers it to the audience’s channel — the same livesN for all three types.
There's no code to install here — this repo is the definition the bot reads. What you need is the bot running, a HeyGen account, and the channel folders.
With this repo declared in config/fluxos.json.
# in the authorized chat /fluxos /promoavatar3 help
Three avatars per audience, recorded by hand — that’s the real cost of this flow.
# the name must be exact C<N>-<alvo>-v<versao> # e.g.: C7-jovens-pro-v1
Derived from the audience's channel, just like promoavatar.
mkdir -p ~/projetos/yt-pub-lives24/imports/videos
Commands typed in the Telegram chat with the authorized bot.
All 36 are defined, but running all 36 at once means 36 avatars generated by hand. The usual approach is to filter by audience. | sombra prints phase × target × queue × task and doesn't enqueue anything.
/promoavatar3 <assunto> | alvos=jovens-alc | sombra
The recommended way to start: one audience, all three types — so you can publish in reach → authority → promotional order and compare.
/promoavatar3 <assunto> | alvos=jovens-alc,jovens-aut,jovens-pro /promoavatar3 <assunto> | legenda # default is NO captions /promoavatar3 <assunto> | versao=2 # changes the title's -vN
If you don’t write one, the prompt tells the agent to take a side and record it in the resumo-estrategico.md which one landed and why. But your position takes precedence over theirs — write your own, along with a concrete fact (so the PROOF line isn't empty) and the question you want in the comments.
# opinions are allowed; invented facts are not # (rules 9 and 10 of the prompt still apply)
Because the summary states the chosen position, you can disagree with it before generating any avatars. Here, that applies three manual renders per audience, not one.
/status C#7 # phase × target, and the titles /refazer C#7 jovens-alc # only the target that didn't turn out well
The suffixes are alc/aut/pro, no alcance/promocional: the long title has already been truncated in HeyGen in production, breaking the match. One character off and the download phase can't find anything.
C7-jovens-alc-v1 C7-jovens-aut-v1 C7-jovens-pro-v1
/aprovar unlocks downloading and assembling the reels. If a target fails, redo only that one.
/aprovar C#7 /status C#7 /cancelar C#7 [alvo]
Reach first (brings people in), authority next (turns attention into trust), promotional last (turns trust into clicks).
# -alc → -aut → -pro
Attention: flow.json and the prompt are copied into the flow when it’s created. Editing them here only affects NEW flows — an ongoing flow doesn’t change its rules midway. To apply them to an existing one, create another.