items

# items - the credo work-item model A work item is a single Markdown file under `.credo/items/`. The **folder the file lives in is the only source of truth for its status**. There is no status field, no marker, no task-tracker entry - an item changes status by physically moving between folders. This is deliberate anti-drift: multiple status sources drift out of sync, one physical location cannot. `.credo/items/` IS the task system; do not mirror items into a separate task list. > **Task backend.** If the task backend is `gsd` (set in `.credo/config` as `task_backend`, or via the `CREDO_TASK_BACKEND` env override; resolve with `credo-config.sh backend`), the credo item system is inactive - GSD's > phases are the task system for this project. Do NOT create or move `.credo/items/`; use > GSD's workflow instead. This skill applies only when the backend is `credo` (the default) > or `none`. ## Status = folder (the only truth) The folder tree (created by `credo-init`) and what each folder means: ``` .credo/items/ 1_todo/ 1_clarify/ open questions - needs the user, NOT buildable yet 2_go/ clarified and approved - buildable (go-gate: only 2_go is buildable) 2_done/ Definition of Done met (agent and/or user), gate passed 3_verified/ USER-ONLY - human-in-the-loop confirmation (an agent never places here) 4_archived/ abandoned / deprecated / rejected parked/ hold/ blocked by an external dependency future/ del...