|
| 1 | +# Archived Notes Policy Inventory |
| 2 | + |
| 3 | +Generated: 2026-04-12 |
| 4 | +Scope: `docs/archive/` policy surface only (non-destructive, docs-only lane). |
| 5 | + |
| 6 | +## Source-Of-Truth Baseline (Existing Cleanup Evidence) |
| 7 | +- `docs/dev/reports/cleanup_live_reference_inventory.txt` (Target 4): |
| 8 | + - Exact path: `docs/archive/` |
| 9 | + - Exists: yes |
| 10 | + - Assessment: `live-reference` |
| 11 | + - Notes: archive location is active/documented; policy item still incomplete. |
| 12 | +- `docs/dev/reports/cleanup_keep_move_future_delete_matrix.md`: |
| 13 | + - Target row: ``docs/archive/` archived-notes policy`` |
| 14 | + - Proposed classification: `keep` |
| 15 | + - Recommended future scope: policy-definition PR. |
| 16 | + |
| 17 | +## 1) Path Existence And Archive Contents |
| 18 | +- `docs/archive/` exists: **yes** |
| 19 | +- Recursive file count under `docs/archive/`: **446** |
| 20 | +- Recursive directory count under `docs/archive/`: **5** |
| 21 | + |
| 22 | +Exact directories under `docs/archive/`: |
| 23 | +- `docs/archive/dev-ops` |
| 24 | +- `docs/archive/generated-reports` |
| 25 | +- `docs/archive/pr` |
| 26 | +- `docs/archive/generated-reports/dev-reports` |
| 27 | +- `docs/archive/pr/legacy-pr-history` |
| 28 | + |
| 29 | +Exact file inventory command used: |
| 30 | +```powershell |
| 31 | +rg --files docs/archive |
| 32 | +``` |
| 33 | + |
| 34 | +## 2) Active References To `docs/archive/` |
| 35 | +Reference scan command used: |
| 36 | +```powershell |
| 37 | +rg -n "docs/archive/" docs tools src games samples tests --glob "!docs/archive/**" --glob "!**/node_modules/**" |
| 38 | +``` |
| 39 | + |
| 40 | +Unique active consumer files found: |
| 41 | +- `docs/README.md` |
| 42 | +- `docs/repo-directory-structure.md` |
| 43 | +- `docs/getting-started.md` |
| 44 | +- `docs/review-checklist.md` |
| 45 | +- `docs/architecture/repo-operating-model.md` |
| 46 | +- `docs/architecture/engine-api-boundary.md` |
| 47 | +- `docs/dev/README.md` |
| 48 | +- `docs/dev/paths.md` |
| 49 | +- `docs/dev/file_tree.txt` |
| 50 | +- `docs/dev/codex_commands.md` |
| 51 | +- `docs/dev/validation_checklist.txt` |
| 52 | +- `docs/dev/reports/README.md` |
| 53 | +- `docs/dev/reports/cleanup_live_reference_inventory.txt` |
| 54 | +- `docs/dev/reports/cleanup_keep_move_future_delete_matrix.md` |
| 55 | +- `docs/dev/reports/BUILD_PR_REPO_CLEANUP_AND_ROADMAP_UPDATE_report.md` |
| 56 | +- `docs/dev/reports/BUILD_PR_TARGETED_REPO_CLEANUP_PASS_1_report.md` |
| 57 | +- `docs/dev/reports/cleanup_execution_guard.md` |
| 58 | +- `docs/dev/reports/cleanup_target_enforcement_map.md` |
| 59 | +- `docs/dev/reports/cleanup_target_normalization_report.md` |
| 60 | +- `docs/dev/reports/templates_validation_guard.md` |
| 61 | +- `docs/dev/reports/docs_path_cleanup_plan.txt` |
| 62 | +- `docs/pr/PLAN_PR_DOCS_ARCHIVE_CLEANUP.md` |
| 63 | +- `docs/pr/BUILD_PR_DOCS_ARCHIVE_CLEANUP.md` |
| 64 | +- `docs/pr/BUILD_PR_TARGETED_REPO_CLEANUP_PASS_1.md` |
| 65 | +- `docs/pr/BUILD_PR_TARGETED_REPO_CLEANUP_PASS_3_ARCHIVED_NOTES_POLICY.md` |
| 66 | + |
| 67 | +### Reference Classification (Policy / Structure / Navigation / Historical) |
| 68 | +| File | Classification | Notes | |
| 69 | +| --- | --- | --- | |
| 70 | +| `docs/README.md` | structure/navigation | Canonical docs entry points include archive destinations. | |
| 71 | +| `docs/repo-directory-structure.md` | structure | Declares archive folders as part of repo structure. | |
| 72 | +| `docs/getting-started.md` | navigation | Explains archive location for onboarding. | |
| 73 | +| `docs/review-checklist.md` | policy | Review rules cite archive destinations. | |
| 74 | +| `docs/architecture/repo-operating-model.md` | policy/structure | Operating model includes archive paths. | |
| 75 | +| `docs/architecture/engine-api-boundary.md` | policy | Boundary guidance references archived outputs. | |
| 76 | +| `docs/dev/README.md` | structure/navigation | Dev docs index references archive subpaths. | |
| 77 | +| `docs/dev/paths.md` | policy/structure | Explicit path constants map to archive locations. | |
| 78 | +| `docs/dev/file_tree.txt` | historical/structure | Snapshot includes archive tree placement. | |
| 79 | +| `docs/dev/codex_commands.md` | policy | Command constraints include archive protections. | |
| 80 | +| `docs/dev/validation_checklist.txt` | policy | Validation wording references archive destination. | |
| 81 | +| `docs/dev/reports/README.md` | navigation/policy | Report retention guidance points to archive reports path. | |
| 82 | +| Cleanup reports/specs listed above | policy | Cleanup governance tracks archive target and guard rules. | |
| 83 | +| Docs archive cleanup plan/build specs | historical/policy | Historical movement plan and manifest contract references archive destination. | |
| 84 | +| Current archived-notes policy BUILD spec | policy | Defines this exact policy lane scope/constraints. | |
| 85 | + |
| 86 | +## 3) Required Separation |
| 87 | + |
| 88 | +### Direct path references |
| 89 | +- Direct literal `docs/archive/` references are present and active in the unique consumer files listed above. |
| 90 | + |
| 91 | +### Documentation/policy references |
| 92 | +- All current active references found by scan are documentation/policy/governance surfaces under `docs/`. |
| 93 | + |
| 94 | +### Test/config references |
| 95 | +Commands used: |
| 96 | +```powershell |
| 97 | +rg -n "docs/archive/" tests --glob "!**/node_modules/**" |
| 98 | +rg -n "docs/archive/" --glob "*.json" --glob "*.yml" --glob "*.yaml" --glob "!**/node_modules/**" |
| 99 | +``` |
| 100 | +Result: |
| 101 | +- No test references found. |
| 102 | +- No JSON/YAML config references found. |
| 103 | + |
| 104 | +## 4) Path Assumptions That Block Safe Move/Delete |
| 105 | +1. Documentation contracts currently encode specific archive destinations: |
| 106 | + - `docs/archive/dev-ops/` |
| 107 | + - `docs/archive/generated-reports/` |
| 108 | + - `docs/archive/pr/legacy-pr-history/` |
| 109 | +2. Cleanup governance artifacts already track `docs/archive/` as a retained policy target. |
| 110 | +3. Existing archive-cleanup plan/build specs depend on the exact archive destination path for manifest-based movement and rollback. |
| 111 | +4. Moving/deleting archive paths would require synchronized updates across multiple docs governance surfaces to avoid broken navigation/policy references. |
| 112 | + |
| 113 | +## 5) Inventory Conclusion |
| 114 | +- `docs/archive/` is an active policy/structure target with live documentation references. |
| 115 | +- Current evidence supports a conservative keep/defer posture in this lane. |
| 116 | +- No movement, deletion, or rewrite action is justified in this BUILD. |
0 commit comments