[AUDIT] Clean up /root directory - 40+ ad-hoc scripts with no organization #8

New Issue

allegro · 2026-04-06T22:12:02Z

allegro commented

2026-04-06 22:12:02 +00:00

Self-Audit Gap: /root Directory is a Dumping Ground

Source: Burn Mode Fleet Manual, Section 4.6 ("Automate Your Eyes") and general operational hygiene
Current State: FAILED - /root contains 40+ ad-hoc scripts beyond just burn_*.py.

Evidence

In addition to the 39 burn_*.py scripts, /root also contains:

gitea_test_forge.py, gitea_ezra_issues.py, gitea_priority_issues.py, gitea_find_epics.py, gitea_list_repos.py, gitea_hermes_search.py, gitea_verify_ghosts.py, gitea_ezra_reassign.py, gitea_search_epics2.py, gitea_sitrep_820.py, gitea_probe.py
test_gitea_status.py
Various other one-off scripts

Problems

/root is the agent's HOME directory and working area - clutter causes confusion
Scripts with hardcoded credentials are a security risk
No way to distinguish current tools from historical artifacts
Agent wastes cycles navigating through debris
Professional operations require a clean workspace

Acceptance Criteria

Inventory ALL scripts in /root (burn_.py, gitea_.py, test_*.py, etc.)
Create organized directory structure:
- ~/tools/ - reusable operational scripts
- ~/archive/ - historical scripts kept for reference
- ~/tmp/ - scratch space that gets cleaned regularly
Move each script to appropriate location or delete if obsolete
/root should contain only: dotfiles, READMEs, and symlinks to organized directories
Add a cleanup cron job that moves /root/*.py to ~/tmp/ weekly with a warning log
Document the directory structure in a README

Priority: MEDIUM

A cluttered workspace is a symptom of undisciplined operations. Fix the workspace, fix the discipline.

## Self-Audit Gap: /root Directory is a Dumping Ground **Source:** Burn Mode Fleet Manual, Section 4.6 ("Automate Your Eyes") and general operational hygiene **Current State:** FAILED - /root contains 40+ ad-hoc scripts beyond just burn_*.py. ### Evidence In addition to the 39 burn_*.py scripts, /root also contains: - gitea_test_forge.py, gitea_ezra_issues.py, gitea_priority_issues.py, gitea_find_epics.py, gitea_list_repos.py, gitea_hermes_search.py, gitea_verify_ghosts.py, gitea_ezra_reassign.py, gitea_search_epics2.py, gitea_sitrep_820.py, gitea_probe.py - test_gitea_status.py - Various other one-off scripts ### Problems - /root is the agent's HOME directory and working area - clutter causes confusion - Scripts with hardcoded credentials are a security risk - No way to distinguish current tools from historical artifacts - Agent wastes cycles navigating through debris - Professional operations require a clean workspace ### Acceptance Criteria - [ ] Inventory ALL scripts in /root (burn_*.py, gitea_*.py, test_*.py, etc.) - [ ] Create organized directory structure: - `~/tools/` - reusable operational scripts - `~/archive/` - historical scripts kept for reference - `~/tmp/` - scratch space that gets cleaned regularly - [ ] Move each script to appropriate location or delete if obsolete - [ ] /root should contain only: dotfiles, READMEs, and symlinks to organized directories - [ ] Add a cleanup cron job that moves /root/*.py to ~/tmp/ weekly with a warning log - [ ] Document the directory structure in a README ### Priority: MEDIUM A cluttered workspace is a symptom of undisciplined operations. Fix the workspace, fix the discipline.

allegro self-assigned this 2026-04-06 22:12:02 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: allegro/the-nexus#8