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:
– HTML only: `

`, `

`, `
• ` – no headings, no markdown, no other tags
  – Do NOT invent specific facts not implied in the snippet or given fields
  – CAN use general/standard sector language appropriate to the role, naturally, without treating assumptions as facts
  – Keep text truthful, professional, legible
  – Write entirely in Brazilian Portuguese, natural, clear, no unnecessary anglicisms
  – Target size: ~700 words
  – Output ONLY the HTML description – no title, no intro, no code block markers

  2. **Analyze the Input Data:**
  – Cargo: Estágio Fiscal (Fiscal Intern)
  – Empresa: Arttha Gestão & RH
  – Localização: Salvador, Bahia
  – Truncated snippet:
  – “_ ATENÇÃO_: Você tem _12h para finalizar seu cadastro, teste de perfil e fatores comportamentais._ Após concluir, basta aguardar o nosso retorno para avançarmos com os próximos passos.”
  – Responsabilities/attributions (truncated):
  – “ATIVIDADES A SEREM REALIZADAS: – Importação de xml das notas fiscais (Serviço, Vendas e Compras). – Envio de alíquotas às empresas do simples nacional. – Solicitação de DAM de ISS as prefeituras e envio às empresas,para pagamento. – Organizar as pastas do setor no drive do computad…”

  3. **Identify What’s Given and What’s Not:**
  – Given: Job title, company, location, attention deadline, some core activities (partially truncated)
  – Not given: Specific salary, exact years of experience (it’s an internship, so likely 0 or minimal), specific certifications, full list of benefits, exact number of tasks beyond what’s truncated
  – Constraint Check: “NÃO invente fatos específicos que não estejam implícitos…” I must not invent salary, specific benefits beyond what’s reasonable but not falsified, exact experience years. I can use general language typical for a “Estágio Fiscal” role, but must stay truthful and not present assumptions as confirmed facts.

  What can I infer/expand generally without inventing?
  – General duties of a fiscal intern: data entry, document organization, assisting with tax compliance, using systems, supporting the fiscal team, etc. But I must phrase it carefully: “Auxiliar na importação de XMLs de notas fiscais”, “colaborar no envio de alíquotas”, etc. I should not say “responsável por” as if it’s confirmed beyond the snippet, but I can describe typical activities in a natural way, as allowed: “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.” So I can describe typical tasks of a fiscal intern, but frame them as what the role involves, not as confirmed facts from the company beyond the snippet.

  Actually, re-reading: “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 write general sector-appropriate language, but must not present it as the specific company’s confirmed requirements beyond what’s given. I’ll treat the expanded part as general description of what such an internship typically entails, but keep it grounded and not overclaim.

  – The snippet has truncated activities. I can expand on those specific ones mentioned, and add a couple more that are standard for the role, but I need to be careful not to invent. I can say “entre outras atividades relacionadas ao apoio fiscal” or list the ones given plus maybe one more that’s very standard, but I should probably stick to expanding the given ones naturally, and maybe add a generic “outros afazeres inerentes à função” type of statement, but that might be seen as invented. Better to stick close to the given list, maybe expand the descriptions slightly in a general way, but not add new specific tasks that weren’t hinted at.

  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 add general language, but not specific facts. The truncated part ends with “Organizar as pastas do setor no drive do computad…” – I can complete that thought naturally: “no computador” but not invent what exactly they do beyond that. I can expand on the four listed activities by giving a bit more context about what they involve, without making up details.

  Let’s list the given activities:
  1. Importação de xml das notas fiscais (Serviço, Vendas e Compras)
  2. Envio de alíquotas às empresas do simples nacional
  3. Solicitação de DAM de ISS as prefeituras e envio às empresas, para pagamento
  4. Organizar as pastas do setor no drive do computad… (likely “computador”)

  I can expand each of these with a sentence or two of general explanation about what they involve in a fiscal intern role, but keeping it factual and not invented. E.g., “Importação de XMLs de notas fiscais referentes a serviços, vendas e compras, visando o registro e organização da documentação fiscal.” That’s general but descriptive.

  For the “ATENÇÃO” part: I can include the deadline and the process, as it’s given.

  Now, about the structure: HTML only, using `

  ` and `

  /
  • `. No headings. So I need to output just HTML paragraphs and lists. The whole description should be in HTML format, no markdown, no title, no intro text outside HTML. The prompt says: “Produza SOMENTE o HTML da descrição, nada além disso (sem título, sem introdução, sem marcação de bloco de código).” So I should output just the HTML content, starting directly with `

    ` or `

    `, etc.

    Target: ~700 words. That’s quite long for just HTML

    and

    • . I need to fill approximately 700 words in HTML format using only those tags. I can have multiple `

      ` and `

      • ` blocks. I need to be careful to keep it valid HTML, no headings. I can use paragraphs and lists to structure text.

        Let’s plan the HTML structure:
        – Maybe start with a paragraph about the company and location (given).
        – Then a paragraph about the opportunity/deadline (given).
        – Then a list of responsibilities, expanding the given ones, using

      • items. I can have multiple
      • per activity, or one
      • per activity. Since the constraint says “use only

        and

        /
        • “, I can use
          • for the responsibilities list, and

            for other text.
            – I need to reach ~700 words. That’s a lot of text in HTML paragraphs and list items. I’ll need to write extensively but naturally, describing the role, the company, the location, the application process, and expanding on the activities with general fiscal intern knowledge, while staying within the “no invented facts” rule.

            Let’s think about how to structure ~700 words with only

            and

            • :
              – I can have several

              blocks with several sentences each.
              – I can have a

              • list for the responsibilities, with maybe 6-8 items, each being a sentence or two (but
              • can contain paragraphs? No,
              • contains flow content, I can put

                inside

              • ? Actually, HTML allows

                inside

              • , but the constraint says “use only

                and

                /
                • “. It might mean I can only use those tags, but I can nest them or use them as block elements. To be safe, I’ll just use
                • with text directly, or

                  inside

                • if needed, but maybe better to just have text in
                • . However,
                • can have text directly. I can also have multiple

                  and

                  • blocks throughout.

                    Wait, the constraint: “use only

                    and

                    /
                    • , without headings, without markdown”. This likely means the output HTML should only contain those tags, no
                      

                      ,

                      ,

                      , , etc. But

                      and

                      • are enough for structure. I can use

                        for paragraphs,

                        • for lists. I should avoid
                          , , maybe? It says “use only

                          and

                          /
                          • “. Strictly, that means no other tags. So I cannot use , ,
                            . I must rely on plain text within those tags. I can still have text with punctuation. I just can’t use other HTML tags. So I’ll write text, and wrap blocks in

                            or

                            • . No bold or italics via tags; I can rely on
                              • Empresa: Arttha Gestão & RH
                              • Localização: Salvador, Bahia
                              • Categoria da Vaga: Unknown
                              • Tags da Vaga: Salvador