organize

1# /organize -- Repository Structure
2 
3## Orientation
4 
5**Use when:** Deciding where a file belongs, auditing file placement against the project's conventions, running a naming-convention sweep, or moving files so the tree matches the declared layout.
6 
7**Don't use when:** You want a structural map of code relationships (use `/map`), you want to change code inside files (use `/refactor`), you need disk or artifact cleanup (use `/houseclean`), or you need a single known move executed (use `/refactor move`).
8 
9## Boundary with /refactor
10 
11/organize changes where files live and what they are named. Changing code structure within files (extract, inline, split functions or components, rename symbols) is /refactor. The only in-file edits /organize makes are import-path updates forced by a move or rename. If an audit reveals a file that should be split or merged, recommend /refactor; do not do it here.
12 
13## Commands
14 
15| Command | Behavior |
16|---|---|
17| `/organize` | Detect convention, audit placement, propose and execute a move plan |
18| `/organize --audit` | Check current files against the manifest, report violations only |
19| `/organize --show` | Display the current organization manifest |
20| `/organize --lock` | Set `locked: true` so the enforcement hook blocks violations |
21| `/organize --unlock` | Set `locked: false` so enforcement is advisory |
22| `/organize where does {file} go` | Single placement decision, no full audit |
23 
24## Protocol
25 
26### Step 1: CHECK
27…