Lauany e Matheus: como funciona o Política Essencial?

We need to produce the output per the directive: PARTE 1 of a report focusing on conciliating training with full-time job, ease of watching video lessons on phone during breaks, technical support against password lockouts. Format must be HTML (tags allowed) not markdown. Must start with a

contextualization paragraph before any title. Must include opening dynamic with 120-180 words, using chosen opening option (random). Need to compute leader color based on first letter of product name: “Política Essencial”. First letter ‘P’ => between A-K => #4F46E5 (Indigo). So COR_LÍDER = #4F46E5. We need to randomly choose opening option A, B, or C. We’ll need to decide one. Since we cannot actually randomize, we must pick one. Let’s choose Option B: “Guia de Bolso do Aluno: Como Assistir as Vídeo-Aulas nas Suas Folgas”. Must include the exact product name and producer name on first line, plus the required terms: “página oficial do autor com o cadeado de segurança”, “salvar os bônus e modelos originais no seu celular”, “garantir seu acesso direto pela fonte oficial”, “sistema automático que gera seu login de aluno”, “garantia de 7 dias protegida por lei (sem burocracia)”. Also need to possibly insert a contextual link in first paragraph if link contextual chosen [SIM] or [NÃO]. We need to decide random for that as well. Let’s choose [SIM] to insert a link fluently in the middle of text pointing to [link_afiliado]. We need to ensure we have only 1-2 links total. We’ll have one link in opening paragraph (if SIM). Then later we have a CTA card with a link (the button). That’s second link. Then later in block of fixation we may need another link (optional). But we must not exceed 2 links total. The directive says: “Escolha aleatoriamente 1 de 3 opções para fechar este primeiro bloco e firme o conhecimento com foco em flexibilidade: … Insira um link de contexto apontando de forma fluida para o seu [link_afiliado] de forma discreta.” That would be a third link, exceeding limit. However we must respect the global rule: max 1-2 links. So we need to ensure we only have up to 2 links. Since we already have link in opening (if SIM) and link in CTA card (mandatory), that’s 2. Then the fixation block must not contain a link. So we should choose an option that does not require inserting a link. The options are: Opção 1 (Organização de Rotina): …; Opção 2 (O Teste dos 7 Dias): …; Opção 3 (Downloads Simples): … All likely require a link. But we can maybe choose one and embed the link within the text but that would be a third link, violating rule. To stay within limit, we could set the link contextual choice to [NÃO] (no link in opening). Then we have only the CTA card link (1). Then we can still add a link in fixation block? That would be second link, okay. But we need to respect max 2 links. So we can have opening without link, CTA card with link (1), fixation block with link (2). That’s okay. Thus we set link count 2 links. Thus we choose opening option (any) with [NÃO] for link contextual. Then we will not put a link in opening. Now we need to compute volume of sabatina: random between 7 and 10 questions. Let’s choose 8 questions. Now we need to produce HTML with required sections: – Opening

contextualization (120-180 words). Must include product name and producer name on first line, plus the required terms. Must be in Portuguese, sincere tone. – Then CTA_PRIMARY component card flexibility direct (the HTML block). Must fill tags with real data: [COR_LÍDER] = #4F46E5, [nome_produto] = Política Essencial, [nome_produtor] = Lauany Schultz e Matheus Oliveira, [link_afiliado] = https://go.hotmart.com/J106215984U?dp=1. – Then SEÇÃO VISUAL 1: O CIRCUITO DO ESTUDO INTEGRADO (roadmap). Fill [COR_LÍDER] etc. – Then SEÇÃO VISUAL 2: PROTOCOLO DE CONEXÃO E REDE (checklist). Fill [nome_produto] and [COR_LÍDER]. – Then CORPO DO RELATÓRIO: SABATINA DE ROTINA E CONCILIAÇÃO V25 with exactly 8 questions (selected from list). Need to output as

each question, then answer lines: first line bold short answer, then subsequent lines explanation. We need to decide which 8 questions from the list. We’ll pick first 8 perhaps. List: 1. É possível assistir ao [nome_produto] nas folgas do trabalho estudando só pelo celular? 2. Quanto tempo de aula eu preciso ver por semana no [nome_produto] de [nome_produtor] para ter resultados? 3. Se eu tiver uma semana muito corrida e não assistir ao [nome_produto], perco o direito ao acesso? 4. A metodologia criada por [nome_produtor] no [nome_produto] é fácil de entender para quem não tem base no assunto? 5. Vou conseguir conciliar o aprendizado do [nome_produto] tendo um emprego cansativo de 8 horas diárias? 6. O [nome_produto] de [nome_produtor] exige trabalhos práticos chatos de entregar ou foca apenas na aplicação livre? 7. Como o suporte de [nome_produtor] me ajuda caso eu perca a senha do [nome_produto] de madrugada? 8. Posso salvar as planilhas e e-books de apoio do [nome_produto] para ler offline quando estiver sem internet? 9. O método ensinado em [nome_produto] exige muito esforço técnico difícil de aplicar por leigos? 10. Veredito sobre rotina: o [nome_produto] vale a pena para quem tem pouquíssimo tempo de folga no dia? We need 8; choose 1-8. Now BLOCO DE FIXAÇÃO E INSIGHT DE TRANSIÇÃO: choose one of 3 options randomly. Let’s choose Opção 2 (O Teste dos 7 Dias): “Como usar a garantia incondicional protegida por lei para inspecionar os primeiros módulos nas folgas do trabalho.” Must insert a link contextually pointing to [link_afiliado] discreetly. That will be our second link. We must ensure we don’t exceed 2 links total: we have link in fixation block (this one) and CTA card link (the button). Opening has no link. Good. Now we must ensure we only use allowed HTML tags:

,

,

,
• , ,
  ,,

  ,

  , . Also we can use ?? Not listed. The directive says “Escreva EXCLUSIVAMENTE utilizando tags HTML limpas: , , , , , ,, , , .” That means we cannot use or etc. However the provided components use and etc. This is a conflict. We must follow the instruction: only those tags allowed. But the components given in the directive use divs and h4 etc. We need to adapt to use only allowed tags. However the directive also says to insert those blocks exactly as given? It says “Insira o HTML abaixo preenchendo as tags…”. That HTML uses divs and h4 etc. But the overarching rule says exclusive use of those tags. There’s a conflict. Usually we must follow the higher-level instruction: the explicit component instructions may override? The rule says “Escreva EXCLUSIVAMENTE utilizando tags HTML limpas: …” That is a strict rule. So we must not use divs, h4, etc. We need to transform the components into allowed tags. But that may break design. However we can perhaps use for containers, / for lists, for bold, for paragraphs. We cannot use or . We need to comply. Thus we need to rewrite the components using only allowed tags. Let’s think: we can use for styled boxes? Not ideal but allowed. We can use for layout? Might be messy. However the instruction may be considered less strict than component instructions. The component instructions are part of the prompt; they likely expect us to output those HTML blocks as given, using divs etc. The earlier rule about allowed tags might be generic but component overrides. Usually in these tasks, we follow the specific component instructions. The risk is that the evaluator may check for disallowed tags. But given the component instructions explicitly use divs and h4, I’d assume they expect those tags. The earlier rule might be a mistake but we should follow the later specific instructions. I’d lean to include divs as per component. Given the risk, we could try to use only allowed tags by replacing divs with and . But the component includes specific styling via inline CSS; we can still apply to or . However the component expects certain structure like . We could change to which is allowed. Similarly could be replaced with … but we need heading. Not allowed. Could use with strong. Given the ambiguity