ara-research-manager

Research provenance tracking captures decisions, experiments, dead ends, and pivots during coding or research sessions. You need it to maintain an auditable trace of your project's evolution and document your thought process for post-task analysis.

Automate session logging by running a research manager tool at the end of your session to scan conversation history. It analyzes user and AI interactions, then updates a dedicated directory with logged findings, significant events, and decisions.

No, provenance tagging for post-task analysis requires careful review. The automated tracking captures events and decisions from conversation history, but researchers must review and tag significant interactions to ensure accurate session logging.

The best way to maintain an auditable trace is to use a research provenance tool that scans conversation history and updates a project directory. This captures claims, heuristics, and pivots, providing a structured record for post-task analysis.

Yes, session logging works for both coding and general research workflows. The provenance tracking mechanism analyzes conversation history and applies to post-task analysis in any session involving user and AI interactions.