The irreducible Jira core — the first epic of the PM substrate that makes Motir a usable standalone product. Built directly on Story 1.4's work_item model: issue types (epic / story / task / bug), the issue detail view, create / edit, customizable per-project status workflows, assignees, and the issue list. After this epic a team can track real work by hand, with zero AI involved. The AI Planning Layer (Epic 7) later generates these same issues — but the manual path is the foundation and must stand on its own.
Re-opened 2026-06-12 — Story 2.7 (work-item type + executor). The 2026-06-12 Epic-7 augmentation surfaced a gap in this core model: a work item carries kind (epic/story/task/bug/subtask) but no executor-routing type (code/design/test/…) — the plan's own type/executor are only PROSE in the description today. Story 2.7 adds them as real fields (a Principle-#11 justified deviation from Jira, whose only type axis is kind), so the AI layer can generate typed leaves (7.3) and route prompts by type (7.6), and a human can filter by type (Epic 6). It lands in Epic 2 — not Epic 7 — because it is a core work-item attribute, which keeps every AI consumer a clean backward dep.