chore: consolidate Syslog Solution code into unified repository structure

- Moved scattered scripts, templates, and documentation into organized directories (applications/, scripts/, assets/).
- Updated .gitignore to strictly exclude secrets, state files, and IDE configs.
- Added comprehensive README.md outlining repository structure and best practices.
- Preserved all existing documentation and technical architecture files.
- Prepared infrastructure/ for AWS Org and Proxmox Terraform management.

applications/Troubleshooting-Home.md

@@ -0,0 +1,124 @@
+# 06 - TROUBLESHOOTING — Home
+**Purpose:** Common issues, error resolutions, and debugging guides for Syslog infrastructure.
+
+## Overview
+
+This section provides solutions for common technical problems across the Syslog infrastructure stack. Each guide includes symptoms, root causes, and step-by-step fixes.
+
+## Troubleshooting Categories
+
+### **Proxmox & Virtualization**
+- VM won't start or crashes
+- GPU passthrough failures
+- Network connectivity issues
+- Storage performance problems
+- Resource allocation errors
+
+### **GPU & Hardware**
+- AMD GPU detection failures
+- ROCm driver installation issues
+- Temperature and cooling problems
+- Performance degradation
+- Compatibility issues
+
+### **AWS Cloud**
+- EC2 instance connectivity
+- S3 bucket access errors
+- VPC networking issues
+- Cost overrun alerts
+- Security group misconfigurations
+
+### **AI Agents & Models**
+- Model loading failures
+- Inference performance issues
+- Agent communication errors
+- API connectivity problems
+- Memory allocation errors
+
+### **Networking & Security**
+- Firewall blocking issues
+- DNS resolution failures
+- SSL/TLS certificate problems
+- Authentication errors
+- Rate limiting and throttling
+
+## Troubleshooting Methodology
+
+### **Step 1: Gather Information**
+- Error messages and logs
+- System status and metrics
+- Recent changes or updates
+- User reports and symptoms
+
+### **Step 2: Isolate the Problem**
+- Reproduce the issue
+- Identify affected components
+- Check dependencies and connections
+- Verify configurations
+
+### **Step 3: Diagnose Root Cause**
+- Check logs and monitoring
+- Test individual components
+- Compare with known working state
+- Identify configuration drift
+
+### **Step 4: Apply Fix**
+- Implement solution
+- Test thoroughly
+- Document the fix
+- Update monitoring alerts
+
+### **Step 5: Prevent Recurrence**
+- Update documentation
+- Add monitoring checks
+- Create automation scripts
+- Train team members
+
+## Quick Reference
+
+### **Common Commands**
+```bash
+# Check system logs
+journalctl -xe --no-pager | tail -100
+
+# Check GPU status
+rocm-smi
+nvidia-smi
+
+# Check network connectivity
+ping -c 4 8.8.8.8
+traceroute google.com
+
+# Check disk space
+df -h
+du -sh /path/to/directory
+
+# Check running processes
+top -b -n 1 | head -20
+ps aux | grep -i process_name
+```
+
+### **Log Locations**
+- **Proxmox:** `/var/log/pve/`
+- **System:** `/var/log/syslog`, `/var/log/messages`
+- **GPU:** `/var/log/kern.log` (dmesg)
+- **AWS:** CloudWatch Logs
+- **Applications:** Application-specific log directories
+
+## Emergency Procedures
+
+### **Critical Issues**
+1. **Service Down:** Check status, restart if needed, investigate root cause
+2. **Data Loss:** Stop writes, assess backup, restore from backup
+3. **Security Breach:** Isolate system, preserve logs, investigate scope
+4. **Performance Crisis:** Throttle traffic, scale resources, optimize
+
+### **Contact Escalation**
+- **Level 1:** System administrators
+- **Level 2:** Technical lead
+- **Level 3:** External support (vendor, consultant)
+- **Level 4:** Emergency response team
+
+---
+
+*This troubleshooting guide is a living document. Update it with new issues and solutions as they are discovered.*