fused-projectslisted

# Driving Fused end-to-end (spec-first, agent-authored) > **Part of the Fused skill set — don't work from it alone.** Load > **`fused-execute`** for how code runs and **`fused-verify`** for scanning and > tests. See **`fused-guide`** for the full set. Fused organises work as **workspace ⊃ project ⊃ UDF**. You — the driving agent — author the specs and the code; Fused supplies the scaffold, the deterministic validators, a spec↔code consistency hook, and the run/deploy machinery. There is **no code-generation command and no API key** in the loop: authoring code *is your job*. Every step goes through the `fused` CLI (there are no MCP tools). User projects live in the `default` workspace at `~/.openfused/workspaces/default/<project>/`. The full loop: ``` user request → pick an environment (local-first for dev) → decompose into projects + UDFs → write spec.md per UDF → user approves SPECS (never code) → author main.py yourself → fused code verify → git commit (the pairing hook keeps spec+code in sync) → fused code run / code test locally → deploy to preview → promote to release (AWS) ``` The **spec is the only artifact the user reviews**. | Step | Command | |---|---| | Create/select an env | `fused env create` / `fused env list` / `fused env show` | | Create a project | `fused project new` (or `project create`) | | Write spec.md / author code | **you write the files** (no command) | | Validate code | `fused code verify` | | Commi