# Inventory: Tracked evidence repository cleanup inventory

Status: complete
Type: inventory
Updated: 2026-07-25
Next Action: none; retain with the completed cleanup record
Parent: work/wp/completed/wp-remove-generated-evidence-from-git.md

## Scope

Tracked and currently untracked files under `work/evidence/`, plus repository-root
Tool Shed backup archives, for a safe separation between durable human-readable
project evidence and raw/generated qualification payloads.

Observed baseline on 2026-07-25:

- 2,065 tracked files under `work/evidence/`
- 189,973,786 tracked working-tree bytes
- 1,488 `.SLG` files and 340 `.bin` files
- nine `.bundle` files totaling 83,462,101 bytes
- Git loose objects totaling approximately 603 MiB
- repeated Codex Desktop crashes while restoring Git/review-heavy tasks

## Items

| Item | Current Location | Decision | Reason |
| --- | --- | --- | --- |
| Tool Shed maps, workpackages, tickets, checklists, inventories | `work/` outside `work/evidence/` | keep tracked | These are the intended project coordination artifacts. |
| Evidence narratives | `work/evidence/**/*.md` | keep tracked | Human-readable conclusions and handoff context are small and reviewable. |
| Evidence manifests and checksums | selected `work/evidence/**/*.json`, `*.sha256`, `*.RESULT`, `*.csv` | keep tracked after review | Compact machine-readable identity and outcome records are useful when they do not embed bulk payloads. |
| Raw target captures | `work/evidence/**/*.bin`, `*.SLG` | migrate then remove from current Git snapshot | Generated binary state causes excessive Git/Codex hydration. |
| Repository bundles | `work/evidence/**/*.bundle` | migrate then remove from current Git snapshot | Large archives duplicate repository content and dominate evidence size. |
| Raw images and photos | `work/evidence/**/*.png`, `*.heic` | review, then migrate by default | Keep only intentionally curated documentation images in Git. |
| Raw transcripts | `work/evidence/**/*.log`, `*.jlink`, large `*.txt` | migrate; retain only concise excerpts/summaries | Generated runtime output belongs in governed artifact storage, not normal source review. |
| Tool Shed backups | `/tool_shed.backup-*.tar` | keep outside Git and ignored | Workspace-local backup payloads are not project source. |
| Future generated evidence | `work/evidence/generated/` | ignore | Standard landing zone for raw captures; manifests remain outside this directory. |

## Recommendations

- Preserve a byte-for-byte external archive and SHA-256 before changing tracking.
- Generate a path/size/hash/classification manifest for audit and rollback.
- Add shared `.gitignore` policy before removing anything from the index.
- Remove generated evidence from the current snapshot first; treat Git-history
  rewriting as a separate owner-approved migration.
- Start a blank Codex task after cleanup rather than forking the affected history.

## Verification

- Every path classified `migrate` exists in the external archive and matches its hash.
- `git ls-files work/evidence` contains only approved narratives/manifests.
- `git status --short` contains no raw generated evidence.
- Tool Shed index generation and stale-path checks pass.
- Source, firmware, scripts, and current dirty work remain byte-identical to the
  pre-cleanup manifest unless intentionally changed by separate work.
