Local folder inventory — `C:\Projects` (10 Oct 2026)¶

Atul's register (MoneyMarche-Projects-README.md, verified 10 Oct) lists 3 folders. There are 18 top-level entries, holding 9 independent clones and 10 worktrees.

1. Clones (independent repositories)¶

Folder	Remote	Branch checked out	Kind	In Atul's register?
`MoneyMarche`	GitLab `money-marche-group/money-marche-digital-engineering-program`	(not read)	Governance repo (work)	Yes
`MoneyMarcheWebsite`	GitLab `money-marche/money-marche-website`	`fix/79-compare-page-fake-zero-return`	WPDev website code	Yes
`money-marche-sandbox`	GitLab `money-marche-testing/money-marche-sandbox`	`evidence/route-cardinality-extraction-20261010` (the register says `feat/mmclone-elementor-link-transform`, so it has changed since)	MMCLONE engineering and evidence sandbox	Yes
`API\api`	GitLab `moneymarche/api`	`api-phase1-staging-release`	API code (one extra folder level)	No
`mm-crons-readonly-audit`	GitLab `moneymarche/mm-crons`	`main`	MM-Cron code, cloned for a read-only audit	No
`MCRM`	GitHub `moneymarche-dev/MCRM`	`docs/p1c-product-boundary-correction-v01`	MCRM work repo	No
`portfolio-engine`	GitHub `moneymarche-dev/portfolio-engine` (by its worktrees)	`feature/issue-313-category-tree`, with untracked data and evidence (per the 10 Oct run record)	PE main checkout	No
`portfolio-engine-batch001-issue315`	GitHub `moneymarche-dev/portfolio-engine`	`feature/issue-315-objective-selection`	Duplicate clone (Gemini pilot batch 1)	No
`portfolio-engine-batch002-issue315`	GitHub `moneymarche-dev/portfolio-engine`	`feature/issue-315-objective-selection`	Duplicate clone (Gemini pilot batch 2)	No
`mm-wt\wpp`	GitLab `moneymarche/wordpress_plugins`	`production-baseline/2026-10-04`	WordPress plugins, production baseline	No

2. Worktrees (linked to a clone above)¶

Folder	Parent clone	Purpose (from its name)
`MCRM-g2-review`	`MCRM`	G2 review
`portfolio-engine-issue315-evidence`	`portfolio-engine`	Evidence for #315
`pe-pr310-fix`	`portfolio-engine`	Fix for PR #310
`mm-wt\mmdep-docs`	`MoneyMarche`	Governance documents
`mm-wt\batch-1`, `mm-wt\batch-2`, `mm-wt\issue-14`	`money-marche-sandbox`	Sandbox batches and an issue
`mm-wt\issue-8`, `issue-9`, `issue-12`, `issue-13`, `test-execution`	Probably `money-marche-sandbox` (same layout; not verified)	Sandbox issues and test runs

3. Not git repositories¶

Folder	What it holds	Suggestion
`ai-sandbox`	MMDEP: `mmdep` (repo), `mmdep_runtime`, `mmdep_hub`, `isolated_workspaces`, `sandbox`, `playground`, `bin`, plus old loose files (`000 orchestrator design-atul.md`, `backlog-atul.md`, `mmdep-seed-v0.1.zip`, test scripts)	Keep. Register the sub-folders; archive the loose files
`testcop`	The Gemini pilot workspace (with its clones inside), an 87 MB zip of it, and small Gemini test scripts	Keep until the pilot is resumed or retired
`website-tests`	Selenium tests, reports, screenshots, agent prompts, `.venv`; not under git	Put under git (it's the shared testing repo mentioned on 10 Oct), or record where its repository is
`MoneyMarche-Labs`	`Python-FastAPI`, `React-Vite` experiments, not under git	Archive candidate
`.continue`	Settings of the Continue editor extension	Leave

4. Findings¶

Duplicate clones: two full Portfolio Engine clones for the Gemini pilot, plus the pilot's own clones inside testcop. The main portfolio-engine checkout sits on the #313 branch with untracked work (data files, evidence, new scripts and tests), which is the "local work bypassing the issue" risk.
15 of 18 entries are not in the register. Its policy ("avoid permanent task-specific directories") isn't being followed by agents: mm-wt holds 10 worktrees.
Mixed nesting: the API clone sits one level down (API\api), and wpp is a clone inside a worktree folder.
Possible sensitive content to check (names only seen, contents not opened): mm-crons-readonly-audit contains dbbackup, sql, insurance, bajaj allianz and suitecrm folders. If these hold database dumps or client records, they should not sit in a working clone. TEA should check them.
MoneyMarcheWebsite\arevalif@cpanel-sh008.webhostingservices.com holds theme files (PHP, CSS, JS, images), apparently downloaded from the hosting server; no configuration files with credentials were seen at that level.

5. Suggested layout (for discussion; nothing moved)¶

C:\Projects\
  README.md                 the register (one row per folder)
  <project>\                one folder per project
    code\                   the code clone (protected main or coder + reviewer)
    work\                   the work repo (specs, evidence, issues)
    wt\<issue>\             temporary worktrees, removed when the issue closes
  ai-sandbox\               MMDEP (unchanged: runtime and hub are never touched)
  _scratch\<agent>\         agents' temporary space, emptied weekly
  _archive\                 retired folders

Moving folders breaks worktree links and editor settings. Any reorganisation should be done by Atul (or by an agent with explicit approval per step), with worktrees removed through git worktree remove first.

Local folder inventory — C:\Projects (10 Oct 2026)¶