fused-projectslisted

# Driving Fused end-to-end (spec-first, agent-authored) > **Part of the Fused skill set — don't work from it alone.** When the output is a > rendered UI (a dashboard or an editable widget), also load **`fused-widgets`**; > for a question/approval/plan UI, load **`fused-feedback`**. 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*. > **Built-in `_core` workspace.** Fused provides a read-only `_core` workspace. > Its source trees are **no longer bundled in the wheel** — they are cloned at > runtime from an external git repo into `~/.openfused/core/`, materializing at > `~/.openfused/core/skills/<project>/` (first boot needs `git` + network). > Its projects (e.g. `task-management`) are > available immediately via `fused dev serve` as > `workspace="_core", project="task-management"`. User projects live in the > `default` workspace (or any named workspace) — `_core` (and any name starting > with `_`) is reserved and cannot be created by users. The full loop: ``` user request → pick an environment (local-first for dev) → decompose into projects + UDFs (py data + json widget) → write spec.md per UDF → user approves SPECS (never code) → author main.