workspace-setup

Create a `workspace/` directory at the project root containing a `README.md` operator router and a compact `PROJECT.md` management view. The router maps where each kind of truth lives, while PROJECT.md tracks purpose, current work, next steps, and open loops.

First classify every existing artifact as stable documentation, workspace coordination, canonical truth, or disposable material. Then propose an exact move table, get approval, and migrate one project at a time while updating links and retiring old paths.

Repository count does not determine workspace count. Create one workspace per independently operated project; a child repository earns its own workspace only when it has a separate work lifecycle, changing state, and operator boundary.

Choose based on the privacy boundary: tracked workspaces are reviewed with the code, local workspaces stay ignored or outside the repository, and mixed setups separate a tracked safe router from ignored local material. Never commit credentials or secret values.

Do not create a workspace for packages, generated directories, dependency checkouts, category folders, or archives unless they have their own work lifecycle. Also stop if `workspace/` already has an unrelated build or package-manager meaning.