Write the problem hypothesis
For [user], the agent loses or retrieves [information] incorrectly across [scope], causing [wrong action or repeated work].
You can name one user, one situation and one measurable consequence without proposing a feature.Evidence observed in TauricResearch/TradingAgents, a Finance project.
Related friction appears in 11 independent repositories. This is stronger than one backlog item, but still requires direct user validation.
Project strength and demand confidence are measured separately.Reporter context: First of all, excellent work on TradingAgents. The architecture, agent coordination design, and historical data pipeline are very impressive. However, I would like to raise a concern regarding a potential evaluation issue in LLM-based backtesting: Temporal Knowledge Leakage from the Base LLM From the documentation and…Excerpted from the public Issue. Read the complete thread before interpreting it.
Recruit: Recruit people who perform the workflow with real controls, reconciliations or reporting deadlines.
Guardrail: Use anonymized or synthetic records and require human review for financial decisions and regulated outputs.
For [user], the agent loses or retrieves [information] incorrectly across [scope], causing [wrong action or repeated work].
You can name one user, one situation and one measurable consequence without proposing a feature.Test one constrained memory scope with a small real dataset and a written expected-recall benchmark.
The system retrieves the right evidence across repeated sessions without leaking or inventing context.Use anonymized or synthetic records and require human review for financial decisions and regulated outputs.Information has value only when it changes action. This page turns one public signal into a bounded validation exercise. It is a research aid, not proof of demand, investment advice or a product recommendation.