workable-item-lifecyclelisted

# Workable Item Lifecycle The workable-items **SQLite DB is the single source of truth** (§11.4.93, tracked in git per §11.4.95). Issues / Fixed / the summaries and their HTML / PDF / DOCX siblings are **generated outputs** (§11.4.12 / §11.4.53 / §11.4.65 / §11.4.106). **Never hand-edit a generated doc** — change the DB and regenerate, or the next regeneration silently reverts your edit. ## Status — closed set (§11.4.15 / §11.4.21 / §11.4.90) `Queued` · `In progress` · `Ready for testing` · `In testing` · `Reopened` · `Operator-blocked` · terminal closure · `Obsolete (→ Fixed.md)` ## Type — closed set (§11.4.16) `Bug` · `Feature` · `Task`. No fourth value. `Task` is the lowest-stakes default when genuinely ambiguous. ## Closure vocabulary is TYPE-AWARE (§11.4.33) | Type | Closure Status | |---|---| | `Bug` | `Fixed (→ Fixed.md)` | | `Feature` | `Implemented (→ Fixed.md)` | | `Task` | `Completed (→ Fixed.md)` | Closing a `Feature` as "Fixed", or a `Task` as "Implemented", is a §11.4.33 violation. All three are semantically equivalent ("closed, positive evidence captured") but the literal must match the Type. ## Closure requires captured evidence — always (§11.4.123 / §11.4.108) An item may be closed **only** with rock-solid captured proof (§11.4.5 / §11.4.69 / §11.4.107). **Forbidden as proof:** metadata-only, configuration-only, absence-of-error, and grep-without-runtime. "Done" means the item's **runtime signature verifies on a clean deployment** (§11.4.108) — sou