# Board & workflow ## How the work is tracked Every initiative, epic, story and card is a Gitea **issue**. Each issue carries: - one `kind/*` label: `kind/initiative` · `kind/epic` · `kind/story` · `kind/task` - one workflow `status/*` label (the four board columns) - (epics/stories/tasks) a **sprint milestone**: `Sprint 0` … `Sprint 7`, `Sprint M` Parents link to children by stable ID in the body; children link to their parent by `#issue-number`. ## Column mapping (status labels) | Column | Label | |---|---| | Backlog | `status/proposed` | | To Do | `status/ready` | | In Progress | `status/in-progress` | | Done | `status/done` | Initial assignment: initiatives/epics → `status/proposed`; **Sprint 0** stories/tasks → `status/ready` (To Do); everything else → `status/proposed` (Backlog). Nothing starts In Progress or Done. ## Milestones `Sprint 0`, `Sprint 1`, `Sprint 2`, `Sprint 3`, `Sprint 4`, `Sprint M`, `Sprint 5`, `Sprint 6`, `Sprint 7`. Sequencing (Sprint M after Sprint 4) is documented here and in `sprints-and-roadmap.md`; milestone objects carry no due dates because the sprint cadence (OD-01/OD-02) is a *proposed default awaiting sign-off*. ## Creating the Gitea Projects board (manual) Gitea's Projects (Kanban) feature has **no REST API** in 1.23.7, so it cannot be created programmatically. To create it in the web UI (labels already agree with the columns): 1. In `Fabrika/PersonalBlog`, open **Projects** → **New Project**. 2. Name it `PersonalBlog Delivery` (template: None/Basic Kanban). 3. Create columns in order: **Backlog**, **To Do**, **In Progress**, **Done**. 4. Add issues as cards. Because every issue already carries the matching `status/*` label, you can also filter the issue list by label and drag issues onto the matching column — the board and the labels stay in sync. ## Numbering reconciliation v1.1 reused `E26`–`E28` (Sprint M), colliding with v1.0 Sprint 7 `E26`. Resolution: v1.0 IDs `E00`–`E26` unchanged; Sprint M epics renumbered `E26→E29` (media pipeline), `E27→E30` (embeds), `E28→E31` (charts/diagrams). Full detail in `programme.md`.