Here’s a thinking process:

1. **Analyze the Request:**
– **Role:** Professional job ad writer in Brazilian Portuguese.
– **Task:** Expand a short, truncated job snippet into a complete, well-organized HTML description.
– **Constraints:**
– Use only `

` and `

/
• ` tags. No headings, no markdown, no other tags.
  – Do NOT invent specific facts not implied in the snippet or provided fields.
  – Can use general/standard sector language appropriate to the role, but treat suppositions as natural descriptions, not confirmed facts.
  – Keep text truthful, professional, legible.
  – Write entirely in Brazilian Portuguese, natural and clear, no unnecessary anglicisms.
  – Target size: ~700 words.
  – Output ONLY the HTML description, nothing else (no title, no intro, no code block markers).

  2. **Analyze the Input Data:**
  – **Job Title:** Auxiliar de Contas a Pagar – Salvador – BA
  – **Location:** Salvador, Bahia
  – **Truncated Snippet:**
  “Auxiliar a Gerência Financeira nas atividades administrativas e envio de documentação; Realizar lançamentos relacionados a contas a pagar no sistema; Elaborar relatórios financeiros; conciliação bancária; Executar outras atividades relacionadas ao setor.”

  3. **Identify What’s Allowed & What’s Not:**
  – **Not allowed to invent:** Specific salary, false certifications, made-up benefits, invented years of experience, fake requirements.
  – **Allowed to use:** General standard sector language for the role, natural descriptions of typical tasks for “Auxiliar de Contas a Pagar”, as long as I don’t present assumptions as confirmed facts. I need to be careful with wording: use phrases like “podem incluir”, “responsabilidades típicas”, etc., or just describe the role in a way that’s consistent with the snippet without claiming specifics.
  – **Must use only:** `

  ` and `

  /
  • `. No headings (`
    

    `-`

    `), no markdown (so no bold, italics via markdown syntax, but I can use HTML inline if needed? The constraint says “use only

    and

    /
    • “. I should probably avoid inline HTML tags like `` or `` unless explicitly allowed, but the constraint says “use only

      and

      /
      • “. I’ll stick to just those tags and plain text inside them. No `
        `, no ``, etc. Just `

        ` and `

        • `.)
          – **Language:** Brazilian Portuguese, natural, clear.
          – **Word count:** ~700 words.

          Wait, 700 words is a lot for just `

          ` and `

          • ` tags. I need to generate a long, detailed but still concise description. I’ll need to expand on the responsibilities using general, standard language for an Accounts Payable Assistant, without inventing specifics. I’ll have to be very careful not to invent facts. I can describe the role’s typical functions based on the snippet, using open-ended or general phrasing that remains truthful.

            Let’s re-read Rule 2: “Você PODE usar linguagem geral e padrão do setor, apropriada ao cargo (ex.: responsabilidades típicas de um ‘Operador de Empilhadeira’), desde que apresente isso de forma natural e não trate suposições como fatos confirmados.” This means I can describe what the job typically involves, but I must frame it carefully, not as absolute facts if they’re generalized. However, the snippet already gives specific tasks: “Auxiliar a Gerência Financeira nas atividades administrativas e envio de documentação; Realizar lançamentos relacionados a contas a pagar no sistema; Elaborar relatórios financeiros; conciliação bancária; Executar outras atividades relacionadas ao setor.” I can expand on these, but I should avoid saying “responsável por X, Y, Z” as if they’re confirmed from the snippet, unless they’re directly from the snippet. I’ll use phrasing like “Entre as atividades, o profissional pode atuar em:”, “O papel inclui:”, etc. But wait, the constraint says “NÃO invente fatos específicos que não estejam implícitos no trecho fornecido ou nos campos dados”. So I can’t add new specific tasks that aren’t implied. But I can generalize or elaborate on the existing ones using standard language. Actually, the snippet lists tasks: administrative assistance to Finance Dept, sending documentation, launching accounts payable in system, elaborating financial reports, bank reconciliation, other sector-related activities. I can expand on these categories, but I need to be careful not to invent new specific tasks. I can use the existing ones as pillars and expand on what they typically entail in general terms, without making up new ones.

            Actually, re-reading: “Você PODE usar linguagem geral e padrão do setor… desde que apresente isso de forma natural e não trate suposições como fatos confirmados.” This gives me leeway to describe the role using standard industry language, as long as I don’t present assumptions as facts. I think I can write a description that expands on the snippet’s points using natural, professional Portuguese, describing the typical scope of an Accounts Payable Assistant, but I must ensure every fact either comes from the snippet or is a general, non-specific statement about the role. I won’t invent “3 years of experience”, “specific software”, “salary”, “benefits”.

            Let’s plan the HTML structure. Only `

            ` and `

            • `. I can have multiple `

              ` paragraphs and `

              • ` lists. I need to reach ~700 words. That’s quite long for HTML with only those tags. I’ll need to pack a lot of text into `

                ` tags. Each `

                ` can be long. I can have several `

                `s and a `

                • ` list for responsibilities. I must avoid headings, so no `
                  

                  ` etc. I’ll start directly with `

                  ` content.

                  Let’s outline the content in Portuguese, expanding on the snippet:
                  – Introduction: The role supports the Finance Management.
                  – Task 1: Administrative assistance and documentation sending. I’ll describe it generally: coordinating documents, ensuring proper filing, supporting the team with administrative routines.
                  – Task 2: Launching accounts payable in the system. Describing the process: entering invoices, verifying data, ensuring correct posting.
                  – Task 3: Elaborating financial reports. Describing: gathering data, preparing summaries, supporting analysis.
                  – Task 4: Bank reconciliation. Describing: matching statements, identifying discrepancies, ensuring cash flow accuracy.
                  – Task 5: Other sector-related activities. General statement.
                  – Requirements/Profile: General, non-specific: attention to detail, organization, knowledge of basic accounting concepts (but not inventing certifications), willingness to learn. I’ll keep it very generic, maybe as a list but without `` or markdown. I can use `

                  • ` for general profile items, but carefully, as they might be seen as “requirements”. I’ll frame them as “perfil desejável” or “atividades que o profissional pode desenvolver”, but I need to be careful not to invent. Actually, I can describe the ideal candidate’s traits in general terms: “busca-se profissional com boa organização, atenção aos detalhes, interesse pela área financeira”, etc. But these are somewhat subjective. I’ll avoid listing them as strict requirements. Maybe just a paragraph on the profile.

                    Wait, the word count target is ~700 words. That’s substantial. I need to generate a lot of text. I’ll focus on expanding each of the snippet’s points into detailed but general descriptions, using the allowed language. I’ll make sure every statement is either directly from the snippet or a generalized, non-specific elaboration that doesn’t invent facts.

                    Let’s start drafting the HTML in my mind, then write it.

                    Structure:
                    – `

                    …` (intro/organization context)
                    – `

                    …` (expanding on assisting Gerência Financeira)
                    – `

                    • …` (list of typical activities, but I’ll be careful: the snippet already lists them, I can rephrase as a list, but each `
                    • ` must not invent. I’ll list what’s in the snippet, maybe slightly rephrased, but as general descriptions. Actually, I can use the list to enumerate the snippet’s points, but I’ll phrase them as “Responsabilidades incluem:” but without a heading. Since no headings allowed, I’ll just start with `
                      • ` directly. But the constraint says “use only

                        and

                        /
                        • “. It doesn’t say I must use both, but I can. I’ll use a mix.)
                          – `

                          …` (bank reconciliation)
                          – `

                          …` (financial reports)
                          – `

                          …` (other activities)
                          – `

                          …` (profile/requirements in general terms)
                          – `

                          …` (closing/location)

                          I need to ensure the total is ~700 words. I’ll aim for around 15-20 paragraphs of ~35-40 words each, plus a list. Actually, 700 words is about 40-50 lines of text. I’ll write substantial paragraphs.

                          Let’s carefully draft content, word by word, ensuring compliance.

                          Key checks:
                          – No invented salary, benefits, certifications, years of experience.
                          – Only `

                          ` and `

                          • ` tags. No nested tags inside `
                          • ` that are forbidden
                            • Empresa: Vagas de Emprego Bahia
                            • Localização: Salvador, Bahia
                            • Categoria da Vaga: Unknown
                            • Tags da Vaga: Salvador