diff --git a/vault-backlog-pilot-plan.md b/vault-backlog-pilot-plan.md index cce23e6..be401c4 100644 --- a/vault-backlog-pilot-plan.md +++ b/vault-backlog-pilot-plan.md @@ -1,17 +1,27 @@ --- -summary: Backlog decision + pilot plan (Planka CE on OVH, live 2026-07-08, phone gate passed 2026-07-09) — Dev + Clients Planka projects with per-repo/per-client boards, kanban WIP flow with human/AI column ownership, thin Ruby gem/CLI + tick, pull-based unified dashboard (digest + SessionStart brief dropped), vault demoted to knowledge layer +summary: "HISTORICAL — Planka backlog pilot plan (live 2026-07-08, RETIRED 2026-07-16 by cc-os ADR-0042: git issues became the single tracker for state and specs). Kept as the record of the pilot design and why it was tried." tags: - scope/global - type/decision - domain/task-management - tool/claude-code - project/cc-os -status: accepted-pilot-live -last_reviewed: 2026-07-10 +status: superseded (ADR-0042, 2026-07-16 — Planka retired) +last_reviewed: 2026-07-16 --- # Backlog system: decision and pilot plan v2 (2026-07-06) +> **Pilot outcome (2026-07-16):** RETIRED. After one week live, all real work flowed +> through git issues while Planka boards held only the plugin's own build cards; the +> wakeup automation already polled issues; the integration rested on a reverse-engineered +> API plus an unpublished lockstep gem. cc-os **ADR-0042** (supersedes ADR-0033) made git +> issues the single tracker for both state and specs; columns collapsed to open/closed + +> labels with a human-only `next` label. Rework: OpenSpec change +> `retire-planka-git-issues-only` in cc-os. Non-repo/ops work moved to the private +> `jared/ops` Forgejo repo. The unified dashboard remains deferred until it is a felt +> pain point. Everything below is the historical pilot design. + Research behind this decision: [[backlog-system-options-research]] (including the same-day second-pass Planka deep-dive and alternatives sweep). **Supersedes the v1 vault-native plan (same day).** v1 chose vault task notes + Obsidian Bases kanban. It was overturned within hours by a requirement clarification, recorded here so the reasoning survives: