Local Project Roots

Scope

This topic records the content nature of local project and archive roots that Vipin may ask about later. It is meant for fast routing and quick answers, not for copying folder contents into the wiki.

For whole-computer routing and importance-based depth across C:/, D:/, and G:/, start with whole-computer-project-map. This page keeps the project/archive root layer beneath that map.

Current Roots

Operating Rule

  • EXTRACTED: The user explicitly clarified that adding these roots to the wiki means adding their content nature, not placing folders inside the wiki.
  • EXTRACTED: For whole-computer maintenance, classify roots by importance before deep reading: active/high-consequence roots get detail; system/cache/download/bulk roots get shallow bucket summaries.
  • EXTRACTED: For D-drive organization, classify roots by role before moving anything. Do not reorganize research experiments, datasets, checkpoints, or active experiment state as part of general cleanup.
  • EXTRACTED: Physical C:/D:/G: file organization now uses the shared D:/agent-resources/skills/vipin/workstation-maintenance skill for dry-run manifests, preflighted approved move batches, broad-approval execution, and rollback manifests. D:/Research remains a hard no-move boundary.
  • EXTRACTED: On 2026-06-01, D-root organization moved 25 classified immediate root directories into D:/_Organized/<bucket>/_RootDirs/... and kept old root paths as junctions. Five classified roots stayed physically at D:/ because Windows denied access or the roots appeared locked; treat them as classified exceptions, not unknown folders.
  • INFERRED: Use this page to answer “where is X?” and “what kind of material is this?” quickly.
  • INFERRED: Before making edits in any external root, rescan that root because folder names and internal contents may change.
  • INFERRED: For quick answers, load the relevant wiki page first; for slow ingest or direct modification, inspect the live external repository.

D-Drive Organization Buckets

Use these buckets when deciding how to tidy D-drive without breaking active work.

BucketCurrent examplesRule
Agent infrastructureD:/devtools, D:/devtools-public, D:/agent-resources, D:/.claudeKeep launchers/config/runtime homes here; public-safe exports go to separate repos.
Research workbenchD:/ResearchRoute through research-project-workbench; do not move or rewrite experiments during infrastructure cleanup.
Approved organization targetD:/_Organized/Downloads, D:/_Organized/Media, D:/_Organized/Temp-Review, D:/_Organized/Coursework, D:/_Organized/Documents-Private, D:/_Organized/Games, D:/_Organized/Tools-ReviewActive destination buckets for the 2026-06-01 approved file moves and D-root move-with-junction organization. Do not create or use new buckets outside workstation-maintenance move batches.
Public/professional portfolioD:/WeipingYan_portfolio; sensitive/application archive roots may now be compatibility junctions into D:/_Organized/Documents-Private/_RootDirsKeep public and sensitive/application material separate; public pages record metadata only.
Coursework/archiveMoved roots under D:/_Organized/Coursework/_RootDirs; locked coursework roots remain at D:/Treat as archive/course material; edit only when asked. Use old D:/<name> paths when compatibility matters because moved roots keep junctions.
Product/project rootsD:/Project, D:/frontend, D:/Healthcare, D:/Game_develop, D:/IdeaRescan live roots before claims; add wiki entity/topic pages only for repeatedly used projects.
Media and personal downloadsMoved media/download roots under D:/_Organized/Media/_RootDirs and D:/_Organized/Downloads/_RootDirs; locked personal/download roots remain at D:/Do not publish raw contents; classify by source/type and move only with explicit user approval.
Temporary/tool cachesMoved temp/tool roots under D:/_Organized/Temp-Review/_RootDirs and D:/_Organized/Tools-Review/_RootDirs; .pnpm-store remains record-onlyCleanup candidates after checking no active process or repo depends on them.
Vendor/system/bulkD:/Docker, D:/VirtualBox, D:/Drivers, D:/Program Files, D:/System Volume Information, D:/pagefile.sysLeave alone unless doing a dedicated storage/system maintenance pass.

Counterpoints and Gaps

  • The current inventory is intentionally shallow and public-safe.
  • Sensitive archives need private-only handling if deeper detail becomes useful.
  • Healthcare roots need especially conservative handling because project code and local storage can sit close to medical records or test health data.
  • Game-save archives should keep binary save files outside wiki/; record routing, file-type interpretation, and inventory locations instead.
  • Some paths are renamed/case-varied relative to user phrasing, so exact path recall should not replace live discovery.
  • Current workstation inventory was refreshed after approved moves on 2026-06-01; bucket assignments are routing guidance, and future move plans should be regenerated from live state.