Standardize Aurora avatar agent
Equos.ai / Restoration Calculator / avatar documentation
Task metadata
Original request
"ele nao entrou..; sera que tem algum problema com o frontmatter?
se sim, so preciso de task e report novamente pra substituir.. Espero que todos os outros assests estejam no report"
Structured task
Problem
The Aurora avatar for the Equos.ai Restoration Calculator needs to be moved into a cleaner and more reliable agent standard. The existing material includes a main brain prompt, first message, session context schema, and multiple knowledge base files, but it needs to be reviewed, consolidated, and prepared as copy-ready blocks for the avatar platform.
Context
Aurora is the virtual assistant inside the Restoration Calculator frontend at https://calc-desmat-avatar-frontend.vercel.app. Its job is to guide users through the calculator, explain form fields, support the map and restoration workflow, interpret results when session data is available, and clarify environmental, economic, and social concepts related to ecological restoration.
This task belongs to the personal tasks taskboard and is meant to preserve the work as a documented follow-up. The linked report embeds all source assets directly, so the taskboard does not need a separate source-assets folder to keep the context available.
Expected
Create a revised Aurora avatar package that is ready to copy into the target avatar/agent platform. The final package should include a reviewed Prompt/Brain, a reviewed first message, a stable knowledge base split into clear sections, and technical notes for passing dynamic frontend/backend session context into Aurora.
The updated standard should keep strict rules against inventing numerical results, overstating financial or environmental certainty, presenting outputs as official technical opinions, or mixing dynamic scenario data into the stable knowledge base.
Notes
Use the report attached to this task as the source of truth for the current assets. Keep stable documentation separate from dynamic session data. Values such as selected country, ecosystem, area, cost, NPV, IRR, carbon absorbed, report text, selected perspective, and visible screen state should come from runtime session context, not from the static knowledge base.
After adding or replacing this task in the repository, run npm run generate:tasks before checking the board.