aiwork-protocollisted

# .aiwork Folder Protocol Repository-local folder for AI work artifacts, organized by feature or task. Artifacts structure thinking in-session and provide context for future sessions when referenced manually. ## Folder layout ``` .aiwork/ 2026-01-27_auth-refactor/ triage.md spec.md ``` - **Folder:** `{YYYY-MM-DD}_{slug}/`, slug lowercase kebab-case, max 40 chars. - **File:** `{type}.md`. Numbering for multiples of same type: - `plan.md` → `plan_2.md` → `plan_3.md` — when one plan was expected, more followed. - `plan_1.md` → `plan_2.md` → `plan_3.md` — when multiple are expected from the start. - Don't mix schemes in one folder. - **Multi-day:** optionally prefix filenames with `{YYYY-MM-DD}_`. Usually 1-2 artifacts per task. Pick types that fit. ## Grouping and restructuring One task = one folder. Drift signals: - Two folders with overlapping scope or near-identical slugs - Cross-folder `references:` / "Source plan: ../..." pointers - Folder that exists only because a ticket number arrived mid-task On drift, propose consolidation: move artifacts into the canonical folder with a `superseded_by:` pointer, or merge under one date. Ask before moving files. A pointer to an epic's `areas.md` is **not** drift — it's a legitimate parent link (see below). Drift is two folders for the _same_ task. ## Epics A folder is dated when its work starts and holds a few hours' to a few days' work. A big idea doesn't fit: months can pass between framing it and finishin