PTENES
Flow C# · 36 targets · human gate

Three videos per audience — and each one has a different different function.

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.

promoavatar3 — three videos per audience
What it is

The promoavatar, with three outputs per audience

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.

3️⃣ Three scripts per audience

The 12 audiences × 3 types = 36 targets, written <publico>-<tipo>: jovens-alc, mulheres-pro, 40mais-aut…

🔤 C# reference

This flow is C#; o promoavatar é A# e o promoclub é P#. The bot rejects references with a mismatched prefix.

📺 Same channel, three functions

The three types for an audience share its channel and trigger — they end up in the same livesN. Recommended order: reach → authority → promotional.

The three types

They aren’t three variations — they serve three functions

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.

📣 -alc · reach

25–40s. Stop the scroll and get shared. The audience comments and shares. CTA: comment / share — never commercial.

🎓 -aut · authority

35–60s. Teach something concrete and be saved. The audience saves and follows. CTA: save / follow / try.

🎯 -pro · promotional

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.

How it works

Three phases, with a pause in the middle

The text phase runs once for the entire flow; download and reel run per target.

1. text (flow scope)→ ⏸️ you record in HeyGen→ /aprovar C#N→ 2. download (by target)→ 3. reel (by target)

1 · text

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.

2 · download

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.

3 · reel

Builds the 9:16 reel and delivers it to the audience’s channel — the same livesN for all three types.

Prerequisites

What needs to be live

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.

inemaccbot running

With this repo declared in config/fluxos.json.

# in the authorized chat
/fluxos
/promoavatar3 help

HeyGen account

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

Channel folder

Derived from the audience's channel, just like promoavatar.

mkdir -p ~/projetos/yt-pub-lives24/imports/videos
User guide · step by step

From topic to three reels

Commands typed in the Telegram chat with the authorized bot.

1

Filter the targets — and check in shadow mode

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
2

Create the flow with all three types for one audience

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
3

Set the position yourself

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)
4

Disagree at the gate, not afterward

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
5

Record with the exact name — abbreviated suffix

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
6

Unlock and track

/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]
7

Publish in the right order

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.