28 lines
		
	
	
		
			1.3 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
			
		
		
	
	
			28 lines
		
	
	
		
			1.3 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
| # 🚨 Human Assistance Required
 | |
| 
 | |
| This file tracks components, issues, or tasks that require human intervention during the autonomous build process.
 | |
| 
 | |
| ## Current Items Requiring Help
 | |
| 
 | |
| | Date | Component | Issue | Priority | Notes |
 | |
| |------|-----------|-------|----------|-------|
 | |
| | 2025-10-28 | N/A | Initial file creation | Low | This file will be populated as issues arise during autonomous execution |
 | |
| 
 | |
| ## Resolution Status Legend
 | |
| - 🔄 **Pending**: Awaiting human review
 | |
| - ⏳ **In Progress**: Being addressed by human
 | |
| - ✅ **Resolved**: Issue fixed, can continue autonomously
 | |
| - 🔄 **Delegated**: Assigned to specific team/resource
 | |
| 
 | |
| ## How to Use This File
 | |
| 1. When autonomous processes encounter an issue they cannot resolve after multiple attempts
 | |
| 2. Add the issue to the table above with relevant details
 | |
| 3. Address the issue manually
 | |
| 4. Update the status when resolved
 | |
| 5. The autonomous process will check this file for resolved issues before continuing
 | |
| 
 | |
| ## Guidelines for Autonomous Process
 | |
| - Attempt to resolve issues automatically first (exponential backoff, retries)
 | |
| - Only add to this file after reasonable number of attempts (typically 5)
 | |
| - Provide sufficient context for human to understand and resolve the issue
 | |
| - Continue with other tasks while waiting for human resolution |