# EVIDENCE ARCHIVE GUIDE
**Last Updated:** 2025-01-07  
**Purpose:** Quick reference for finding and adding documentation

---

## STRUCTURE
/Features/[Feature_Name]/   → Everything about that feature
/System/                     → System-wide items

## HOW TO FIND EXISTING ISSUES

### 1. UI problems affecting multiple features?
- Check: `CRITICAL_INVESTIGATIONS/UI_Architecture/`
- Check: `Cross_Feature_Issues/CROSS_FEATURE_INDEX.md`

### 2. Specific feature broken?
- Check: `Features/[Feature_Name]/CURRENT_STATE.md`
- Check: `Features/[Feature_Name]/BUGS/`

### 3. Database/System issues?
- Check: `DATABASE_ANALYSIS/CRITICAL_ISSUES.md`
- Check: `CRITICAL_INVESTIGATIONS/Database_Analysis/`

### 4. "Is this a known issue?"
- Check: `ACTUAL_CURRENT_STATE.md` (quick overview)
- Check: `System/ERROR_PATTERNS/` (common patterns)

## HOW TO ADD NEW ITEMS

### 1. New bug in Trade Categories?
→ Goes in `Features/Trade_Categories/BUGS/`

### 2. New payment feature?
→ Goes in `Features/Payments/ENHANCEMENTS/`

### 3. System audit?
→ Goes in `System/AUDITS/`

### 4. Sprint planning?
→ Goes in `System/SPRINTS/`

## NAMING CONVENTION
[TYPE]_[description]_[YYYY-MM-DD]/
**Example:** `BUG_dropdown_not_loading_2025-09-06/`

## FOR NEW DEVELOPERS/CLAUDE
1. **Start here:** `README_Developer_Onboarding.md` (reality check)
2. **Then read:** `Features/[Feature_Name]/CURRENT_STATE.md`
3. **For overview:** `ACTUAL_CURRENT_STATE.md`

## QUICK REFERENCE
- **Current platform state:** `ACTUAL_CURRENT_STATE.md`
- **Cross-feature issues:** `Cross_Feature_Issues/CROSS_FEATURE_INDEX.md`
- **Critical investigations:** `CRITICAL_INVESTIGATIONS/`
- **Feature-specific:** `Features/[Feature_Name]/`
- **System-wide:** `System/`

---

*This guide prioritizes finding and filing information quickly. For detailed onboarding, see README_Developer_Onboarding.md*