O Doutor da Máfia (Irmãos Ferraro 5): Análise Técnica e Onde Ler

We need to produce the final HTML page according to all rules. Steps: 1. Start with opening paragraph(s) of 1-2 short paragraphs in

tags, contextualizing the technical analysis before any question. Must mention product name and the word “download” in first paragraph. Also answer main funnel doubts: legitimacy, investment worth, how access works, guarantee. No subtitle. Use journalistic pragmatic tone. 2. Then after opening, insert the CTA_PRIMÁRIO block exactly as given, but replace placeholders with actual data from product. We have product name: “O doutor da máfia – Irmãos Ferraro, 4”. Title content: “O doutor da máfia – Irmãos Ferraro, 4 por Ary Nascimento (Autor)”. Format: eBook Kindle. Stars: 4,9 4,9 de 5 estrelas (227). Additional specs: 5 de 5: Irmãos Ferraro 1º mais vendido em Livros de Ação e Aventura em Romance Homem protetor / Médico x residente / Slow burn / Toque nela e morra / Found Family / Máfia romance / Criança fofa / Hots de tirar o fôlego. etc. We need to extract data: – FORMATO_DO_PRODUTO: eBook Kindle – DIAS_DE_GARANTIA: not provided in technical data. We need to infer from “GARANTIA:” field; it’s not listed in [dados_tecnicos] but we have “GARANTIA:” maybe not included. In the technical specs, there is “Aviso: História com conteúdo impróprio…” but no explicit guarantee days. However rule says if GARANTIA not present, use default 7 days. So DIAS_DE_GARANTIA = 7. – PLATAFORMA_DE_MEMBROS: “plataforma de membros” mentioned as “área de membros da plataforma [NOME_DA_PLATAFORMA_DE_MEMBROS]”. Not given a name. Could be “Plataforma de Membros”? But we need to fill with something. Maybe we can infer it’s the platform where the eBook is sold; not given. Could use generic “Plataforma de Membros”. But maybe we can use “área de membros” as name? The placeholder expects a label. Could use “Plataforma de Membros”. We’ll put “Plataforma de Membros”. – NOME_DA_PLATAFORMA_DE_MEMBROS: same as above? Actually in CTA block they use [NOME_DA_PLATAFORMA_DE_MEMBROS] for badge and footnote. So we can set “Plataforma de Membros”. – PRECO: not given. Not needed in badges maybe omitted if not present. But we need to generate badges for each field available in [dados_tecnicos]. The list includes: PRECO, GARANTIA, CARGA_HORARIA, SUPORTE, CERTIFICACAO, COMUNIDADE, BONUS, ATUALIZACOES. From given data we have: – PRECO: not provided. – GARANTIA: not provided (we will use 7 days default) – CARGA_HORARIA: not provided. – SUPORTE: not provided. – CERTIFICACAO: not provided. – COMUNIDADE: not provided. – BONUS: not provided. – ATUALIZACOES: not provided. But we still need to output badges for each field that is available? The instruction: “Gere um badge para cada campo disponível em [dados_tecnicos]”. So we only generate badges for fields that are present. Since none of those fields are present in the provided data, maybe we skip? But we could still generate badges with placeholder? Better to generate badges only for fields that have values. Since none are present, maybe we output no badges? But the structure expects some badges. Could we include “PRECO:” etc with unknown? Might be okay to include with “Não informado”. But that would be adding info not in data. Might violate rule to not invent. So we should only include badges for fields that are actually present. Since none are present, maybe we output nothing? But the block expects badges. Could we include a badge for “FORMULARIO”? Not in list. Hmm. Maybe we can treat “FORMATO:” as part of data? Not in list. The list is specific. So maybe we should output an empty badge section? But the HTML code includes a comment “BÁDGE” and expects to fill. If we output nothing, the div will be empty, which may break layout but okay. Given constraints, perhaps we should include a badge for “FORMATO” is not allowed. So maybe we just leave the badge div empty. But that may be considered missing required component. However rule says generate a badge for each field available; if none, then no badge. I’ll output a badge for “GARANTIA: 7 dias” as we derived, but GARANTIA is not in list but we can still include? The list includes GARANTIA, so we can include it even if not originally in data? The data didn’t have GARANTE field, but we can infer. Might be okay. But to be safe, we can include a badge for “GARANTIA: 7 dias”. That’s a field we have value for. The list includes GARANTIA, so we can generate a badge for it. Also we can generate a badge for “FORMATO: eBook Kindle”? That’s not in list but maybe we can treat as part of product description. But not required. I’ll generate badges for: – FORMATO: eBook Kindle (not in list but maybe okay) – GARANTIA: 7 dias – PLATAFORMA: Plataforma de Membros – PRODUTO DIGITAL OFICIAL (this is a fixed badge text) But the badge template uses label and value; we can customize label. The given badge HTML uses placeholder [FORMATO_DO_PRODUTO], [DIAS_DE_GARANTIA], [NOME_DA_PLATAFORMA_DE_MEMBROS], and fixed “PRODUTO DIGITAL OFICIAL”. So we need to replace those placeholders with actual values. Thus: – [FORMATO_DO_PRODUTO] -> “eBook Kindle” – [DIAS_DE_GARANTIA] -> “7” – [NOME_DA_PLATAFORMA_DE_MEMBROS] -> “Plataforma de Membros” The fourth badge “PRODUTO DIGITAL OFICIAL” stays same. Thus we need to output those four badges. Now after CTA_PRIMÁRIO, we need to continue with sections according to the calculated route. We need to determine group based on first letter of product name. Product name starts with “O”. That’s letter O. Which group does O belong to? The groups defined: Group 0 [A,F,K,P,U,Z]; Group 1 [B,G,L,Q,V]; Group 2 [C,H,M,R,W]; Group 3 [D,I,N,S,X]; Group 4 Others. O is not in any listed group, so falls under “Outros” -> Group 4. Thus we use Group 4 route: ABERTURA_FUNIL → CTA_PRIMÁRIO → SEÇÃO_PRODUTO → SEÇÃO_DIAGNOSTICO → SEÇÃO_GARANTIA → SEÇÃO_DOWNLOAD_MEMBROS → SEÇÃO_CHECKLIST → CTA_FINAL Thus after CTA_PRIMÁRIO, we need to add SEÇÃO_PRODUTO (150-220 words) with

and an emoji, then a line in italics, then SEÇÃO_DIAGNOSTICO (also 150-220 words) with

and emoji, etc. But the instructions say “Execute as seções do Roteiro Ativo calculado. Cada seção: 150 a 220 palavras. Abra cada uma com

editorial com 1 emoji — nunca use o nome técnico da seção como título.” We need to produce sections: SEÇÃO_PRODUTO, SEÇÃO_DIAGNOSTICO, SEÇÃO_GARANTIA, SEÇÃO_DOWNLOAD_MEMBROS, SEÇÃO_CHECKLIST, CTA_FINAL. But also need to include SEÇÃO_GARANTIA block (blockquote) after second textual section. Actually SEÇÃO_GARANTIA is mandatory and should appear after the second textual section. In the flow, after SEÇÃO_PRODUTO (first textual section), then SEÇÃO_DIAGNOSTICO (second textual section). After that, we must include SEÇÃO_GARANTIA block (blockQuote). Then SECTION_DOWNLOAD_MEMBROS (aside). Then maybe SECTION_CHECKLIST? Actually the route includes SECTION_CHECKLIST after SECTION_DOWNLOAD_MEMBROS? The order: SEÇÃO_PRODUTO → SEÇÃO_DIAGNOSTICO → SEÇÃO_GARANTIA → SEÇÃO_DOWNLOAD_MEMBROS → SEÇÃO_CHECKLIST → CTA_FINAL. Yes. Thus we need to produce: – SECTION_PRODUTO:

with emoji, 150-220 words, mention product name at most once. – SECTION_DIAGNOSTICO:

with emoji, 150-220 words. – Then SECTION_GARANTIA blockquote (as specified) with guarantee text. – Then SECTION_DOWNLOAD_MEMBROS aside. – Then SECTION_CHECKLIST: a checklist (

• ) of prerequisites. Must be 150