vsalisted

# VSA — Slice Placement & Isolation The architecture in one breath: **group by feature slice, not file type; slices never import each other; modules talk only through database state and events; the scheduler is the only orchestrator.** Default mode is **place**; the words "audit", "scan", "violations", "leak" select **audit**. ## The Rules (both modes enforce these) 1. **Slice = one user story.** Every class serving that story — controller, service, job, listener — lives in the same folder. Namespace: `App\{Module}\{Slice}\{ClassName}`. 2. **No type folders.** `Actions/`, `Jobs/`, `Listeners/`, `Http/Controllers/` are banned; the moment one appears, slicing has failed. 3. **No cross-slice imports.** A slice never `use`s or dispatches a class from another slice. 4. **Shared within a module → module root.** A class, DTO, or enum used by 2+ slices of the same module moves to `app/{Module}/` — never defined in one slice and imported by another. 5. **Events are the seams.** - Slice must trigger a sibling slice → fire a module-internal event at the **module root**; the receiving slice registers a listener. Never a direct call or job dispatch across the boundary. - Event consumed by 2+ modules → `App\Shared\Events\`. - An event never lives inside a slice folder. 6. **Modules never import each other's classes.** Cross-module effects flow through database state (status fields another module's scheduler picks up) or shared events. Models used by many modules live in `App\S