Reports

Reports is the memory layer of GetProa.

It turns generated analysis into reusable context for future decisions.

Core Purpose

Use Reports to:

• Retrieve previous analyses quickly
• Track processing state and delivery status
• Reopen report context when re-evaluating decisions

Typical Workflow

1. Open reports list
2. Scan by status and recency
3. Open completed reports for review
4. Revisit pending/processing items later
5. Use report history to guide next actions

Status Model

What Good Usage Looks Like

• You name and organize context around each report cycle
• You revisit prior reports before major new decisions
• You compare "what we expected" vs. "what happened"
• You use reports to improve process, not only to store files

Practical Review Routine

For each completed report, capture:

• Main conclusion
• Supporting evidence
• Decision taken
• Follow-up trigger

This creates decision continuity across weeks and months.

Common Mistakes

1. Treating reports as archives without review
2. Ignoring failed reports without root-cause check
3. Creating new reports without closing prior decision loops
4. Not linking reports to subsequent portfolio actions

Cross-Module Connection

• Use report outcomes to adjust Investments structure
• Link monthly patterns from Budget to decision updates
• Use Assistant to find report status, revisit decision memory, or prepare a new report request for review

AI assistant messages and AI reports use separate limits. A report request may count against report quota even when it starts from Assistant.