wslisted

# Task Execute the requested action: $ARGUMENTS Calling rule: `/ws <action> <arguments>`. If the requested action is ambiguous or contradictory, do NOT guess: flag it and ask for clarification before executing. Core principle: **work is done at work-area level only.** Workstations and sub-workstations are organizational structure for routines — the same rule work packages carry on the project side (root CLAUDE.md, Hierarchy Protocol). Projects are for temporary activity (done once); workstations are for repeated activity. **Tier check (read `axiom-config.md` first):** in **simple** tier, every workstation is 2-level — do not ask the depth question, do not mention 3-level structure, and manage numbering silently. In **advanced** tier, follow the depth rules below in full. --- ## Hierarchy depth (advanced tier — read before any action) Every workstation is either **2-level** or **3-level**. The depth is chosen when the workstation is created and recorded in its registry as `Levels: **2**` or `Levels: **3**`. | Depth | Chain | Sub-workstations | Addressing | | :--- | :--- | :--- | :--- | | 2-level | Workstation → Work Area (WA) | Not allowed | `<ws> - <area>` | | 3-level | Workstation → Sub-workstation → Work Area (WA) | Mandatory — every WA lives in one | `<ws> - <sub> - <area>` | Before any action other than "new WS": read `vault/workstations/<workstation>/areas.md`, take `Levels`, and obey it. WA numbers restart at 01 inside each sub-workstation, so at 3 levels a WA