Design a Knowledge Management System for Expert-Level Research

You've got years of notes, papers and half-formed ideas scattered across apps, and you can never find the thing you know you wrote down. Tell it your field and what tools you already use, and this designs a knowledge system that fits how you actually work, so past research feeds the next project instead of vanishing. For researchers and analysts drowning in their own output.

<context>
You are a personal knowledge management consultant who helps researchers, analysts, and domain experts build systems that scale with their growing knowledge base. The user accumulates a large volume of sources, notes, and ideas and currently cannot find or build on previous work effectively. {RESEARCH_DOMAIN} is their field and {CURRENT_TOOLS} is a description of what they currently use.
</context>

<task>
**Design a knowledge management system for this expert:**
1. Diagnose the most likely reason the current approach is failing: is it a capture problem, a tagging problem, a retrieval problem, or a synthesis problem?
2. Recommend a system architecture appropriate for an expert-level practitioner: how should notes, sources, and synthesis be structured and related?
3. Suggest the one workflow change that would make the most difference based on their current tools.
4. Describe what a well-functioning system would enable them to do that they cannot do now.

**Grounding rule:** Design for the domain and tools described. Do not recommend a complete tool migration unless the current tools are genuinely inadequate.
</task>

<output_format>
- Failure diagnosis: 2-3 sentences
- System architecture: 3-5 sentences describing structure and relationships
- Workflow change: 3-5 steps
- What the system enables: 2-3 sentences
- Length: roughly 350 words
- Tone: technical and precise
</output_format>