---
doc_id: SPR-CK8S-INDEX-0001
type: sprint-index
title: "Sprint Index (normalized structure)"
status: active
owner_role: EM
created_at: 2026-02-24
updated_at: 2026-04-01
related_issues: [112, 154, 184, 185, 187, 189, 195, 197, 199, 201, 212, 218, 220, 222, 238, 241, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256, 257, 258, 259, 260, 216, 262, 263, 265, 281, 282, 320, 327, 333, 335, 337, 340, 351, 360, 361, 363, 366, 369, 370, 371, 372, 373, 374, 375, 378, 383, 385, 387, 389, 391, 392, 393, 394, 395, 413, 416, 418, 444, 447, 448, 452, 454, 469, 471, 476, 480, 484, 490, 492, 494, 496, 510, 537, 541, 542, 543, 544, 545, 546, 547, 554, 557, 559, 561, 562, 563, 565, 567, 568, 571, 573, 575, 579, 581, 582]
related_prs: []
approvals:
  required: ["Owner"]
  status: pending
  request_id: "owner-2026-02-24-sprint-index"
---

# Sprint Index

## TL;DR
- Спринты ведутся в структуре `docs/delivery/sprints/s<номер>/`.
- Для каждого спринта сохранён единый формат: sprint plan + epic catalog + day epics + traceability.
- Sprint index хранит только каноническую карту спринтов и ссылки на sprint/epic артефакты.
- Исторические issue-specific updates по спринтам размещаются в `docs/delivery/traceability/s<номер>_*.md` и не дублируются в sprint index.
- Источник процесса: `docs/delivery/development_process_requirements.md`.

## Карта спринтов

| Sprint | План | Каталог эпиков | Статус | Комментарий |
|---|---|---|---|---|
| S1 | `docs/delivery/sprints/s1/sprint_s1_mvp_vertical_slice.md` | `docs/delivery/epics/s1/epic_s1.md` | completed | Базовый MVP vertical slice закрыт (Day0..Day7). |
| S2 | `docs/delivery/sprints/s2/sprint_s2_dogfooding.md` | `docs/delivery/epics/s2/epic_s2.md` | completed | Dogfooding + governance baseline закрыты. |
| S3 | `docs/delivery/sprints/s3/sprint_s3_mvp_completion.md` | `docs/delivery/epics/s3/epic_s3.md` | in-progress | Финальный e2e и closeout выполняются по Day20. |
| S4 | `docs/delivery/sprints/s4/sprint_s4_multi_repo_federation.md` | `docs/delivery/epics/s4/epic_s4.md` | completed (day1) | Execution foundation по multi-repo зафиксирован. |
| S5 | `docs/delivery/sprints/s5/sprint_s5_stage_entry_and_label_ux.md` | `docs/delivery/epics/s5/epic_s5.md` | in-progress | UX-упрощение stage/label запуска и deterministic next-step actions (Issues #154/#155/#170/#171). |
| S6 | `docs/delivery/sprints/s6/sprint_s6_agents_prompt_management.md` | `docs/delivery/epics/s6/epic_s6.md` | completed | Day1..Day11 закрыты: release closeout `#262`, postdeploy `#263`, ops closeout `#265`; сформирован baseline runbook/monitoring/alerts/SLO/rollback. |
| S7 | `docs/delivery/sprints/s7/sprint_s7_mvp_readiness_gap_closure.md` | `docs/delivery/epics/s7/epic_s7.md` | in-progress | Day1..Day5 закрыли intake/vision/prd/arch/design пакет (`#212/#218/#220/#222/#238`), Day6 plan (`#241`) сформировал execution package и по owner-уточнению создал 18 implementation issues `#243..#260` (по одному на `S7-E01..S7-E18`) с parity-check `18/18` перед `run:dev`. |
| S8 | `docs/delivery/sprints/s8/sprint_s8_go_refactoring_parallelization.md` | `docs/delivery/epics/s8/epic_s8.md` | in-progress | Параллельный Go-refactor stream расширен onboarding-потоками; Day4 по `#320` уже внедрил `docs/index.md`, domain `README.md`, migration-map и remediation issue refs. |
| S9 | `docs/delivery/sprints/s9/sprint_s9_mission_control_dashboard_control_plane.md` | `docs/delivery/epics/s9/epic_s9.md` | in-review | Новый product stream для Mission Control Dashboard: Day1..Day5 сформировали product/arch/design baseline (`#333/#335/#337/#340/#351`), а Day6 plan (`#363`) создал execution package и handover issues `#369..#375` с waves для foundation, backend, transport, UI, observability и conditional voice contour. |
| S10 | `docs/delivery/sprints/s10/sprint_s10_mcp_user_interactions.md` | `docs/delivery/epics/s10/epic_s10.md` | in-review | Новый product stream для built-in MCP user interactions: Day1 intake (`#360`), Day2 vision (`#378`), Day3 PRD (`#383`), Day4 architecture (`#385`), Day5 design (`#387`) и Day6 plan (`#389`) сформировали execution package; созданы implementation issues `#391..#395` для owner-managed `run:dev` waves. |
| S11 | `docs/delivery/sprints/s11/sprint_s11_telegram_user_interaction_adapter.md` | `docs/delivery/epics/s11/epic_s11.md` | in-review | Новый последовательный stream для Telegram-адаптера как первого внешнего channel path: Day1 intake (`#361`) зафиксировал зависимость от core Sprint S10, Day2 vision (`#447`) закрепил mission/KPI/guardrails, Day3 PRD (`#448`) зафиксировал user stories/FR/AC/NFR и callback/webhook guardrails, Day4 architecture (`#452`) выпустил ownership/C4/ADR package и создал issue `#454` для `run:design`, а initial continuity issue `#444` 2026-03-14 закрыта как `state:superseded`. |
| S12 | `docs/delivery/sprints/s12/sprint_s12_github_api_rate_limit_resilience.md` | `docs/delivery/epics/s12/epic_s12.md` | in-review | Новый cross-cutting stream для GitHub API rate-limit resilience: Day1 intake (`#366`) зафиксировал controlled wait-state, Day2 vision (`#413`) оформил mission/KPI/guardrails, Day3 PRD (`#416`) закрепил product contract и создал continuity issue `#418` для `run:arch`. |
| S13 | `docs/delivery/sprints/s13/sprint_s13_quality_governance_system.md` | `docs/delivery/epics/s13/epic_s13.md` | in-review | Новый governance stream для `Quality Governance System`: Day1 intake (`#469`) зафиксировал quality metrics baseline, risk tiers, evidence taxonomy, verification minimum и review contract, Day2 vision (`#471`) закрепил mission/KPI/guardrails и proportional governance baseline, Day3 PRD (`#476`) зафиксировал user stories/FR/AC/NFR, expected evidence и proportional stage-gate contract, Day4 architecture (`#484`) закрепил canonical governance ownership, publication discipline и boundary `Sprint S13 -> Sprint S14`, а issue `#494` создана для `run:design`. |
| S16 | `docs/delivery/sprints/s16/sprint_s16_mission_control_graph_workspace.md` | `docs/delivery/epics/s16/epic_s16.md` | superseded | 2026-03-25 issue `#561` перевела Sprint S16 в historical superseded baseline: lane/column shell, taxonomy `discussion/work_item/run/pull_request`, старые freshness semantics и execution handover `#542..#547` больше не являются текущим Mission Control source of truth. Актуальный reset path: `#561` doc-reset -> `#562` frontend-first fake-data sprint -> `#563` backend rebuild после owner approval UX. |
| S17 | `docs/delivery/sprints/s17/sprint_s17_unified_user_interaction_waits_and_owner_feedback_inbox.md` | `docs/delivery/epics/s17/epic_s17.md` | in-review | Новый cross-cutting stream для long-lived owner feedback loop: Day1 intake (`#541`) зафиксировал same live session как primary happy-path, Day2 vision (`#554`) закрепил mission/KPI/guardrails, Day3 PRD (`#557`) формализовал user stories/FR/AC/NFR, Day4 architecture (`#559`) закрепил ownership/live-wait baseline, Day5 design (`#568`) выпустил implementation-ready contracts, а Day6 plan (`#575`) сформировал execution package `S17-E01..S17-E07` и создал handover issue `#582` для owner-managed `run:dev`. |
| S18 | `docs/delivery/sprints/s18/sprint_s18_mission_control_frontend_first_canvas_fake_data.md` | `docs/delivery/epics/s18/epic_s18.md` | in-review | Новый Mission Control reset-stream после doc-reset `#561`: Day1..Day5 сформировали product/arch/design baseline (`#562/#565/#567/#571/#573`), а Day6 plan (`#579`) выпустил execution package, quality gates и continuity handover issue `#581` для owner-managed `run:dev`; backend rebuild остаётся отдельной задачей `#563` после owner approval UX. |

## Правила структуры
- Sprint-plan: `docs/delivery/sprints/s<номер>/sprint_s<номер>_<name>.md`.
- Epic-catalog: `docs/delivery/epics/s<номер>/epic_s<номер>.md`.
- Day-epic: `docs/delivery/epics/s<номер>/epic-s<номер>-day<день>-<name>.md`.
- Любое изменение статуса спринта синхронно отражается в:
  - `docs/delivery/delivery_plan.md`;
  - `docs/delivery/issue_map.md`;
  - `docs/delivery/requirements_traceability.md`.
- Historical delta по sprint-issue evidence синхронно отражается в релевантном файле `docs/delivery/traceability/s<номер>_*.md`.
