analytics/flow-metrics-v0 #22

New issue

Closed

opened 2026-05-09 23:26:27 +02:00 by codex · 1 comment

codex commented

2026-05-09 23:26:27 +02:00

Collaborator

Parent: #2
Wave: 4 - Analytics Foundation
Depends on: #21

Summary

Compute initial kanban flow metrics from event history without building a heavy dashboard.

Scope

Read-only metrics: lead time, cycle time, throughput, aging WIP, blocked time.
Define cycle start/end conventions for AI Inbox and generic boards.
Keep calculations transparent and explainable.
Return raw supporting event links where useful.

Non-goals

No Nave/GetNave clone dashboard yet.
No probabilistic forecasting.
No automatic management recommendations.

Acceptance Criteria

Metrics can be computed for a board/date range.
Aging WIP identifies cards currently stuck in active columns.
Blocked time uses card relation/blocking history where available.
Results are explainable enough for Iskra to summarize without overclaiming.

Tests / Smoke

Unit tests with fixture timelines.
Edge-case tests for missing/partial history.
API smoke on AI Inbox sample data.

Rollback

Disable metrics endpoint/read model; no data changes expected.

Owner Gates

Owner review of metric definitions before treating them as canonical.

Parent: #2 Wave: 4 - Analytics Foundation Depends on: #21 ## Summary Compute initial kanban flow metrics from event history without building a heavy dashboard. ## Scope - Read-only metrics: lead time, cycle time, throughput, aging WIP, blocked time. - Define cycle start/end conventions for AI Inbox and generic boards. - Keep calculations transparent and explainable. - Return raw supporting event links where useful. ## Non-goals - No Nave/GetNave clone dashboard yet. - No probabilistic forecasting. - No automatic management recommendations. ## Acceptance Criteria - Metrics can be computed for a board/date range. - Aging WIP identifies cards currently stuck in active columns. - Blocked time uses card relation/blocking history where available. - Results are explainable enough for Iskra to summarize without overclaiming. ## Tests / Smoke - Unit tests with fixture timelines. - Edge-case tests for missing/partial history. - API smoke on AI Inbox sample data. ## Rollback Disable metrics endpoint/read model; no data changes expected. ## Owner Gates Owner review of metric definitions before treating them as canonical.

codex referenced this issue

2026-05-09 23:26:33 +02:00

web/flow-health-lite #23

codex referenced this issue

2026-05-09 23:27:13 +02:00

[meta] Kan-ductor maturity waves #2

pdurlej commented

2026-05-10 14:18:50 +02:00

Owner

Resolved by PR #46 (feat(analytics): add flow metrics v0), landed on main via chain drain PR #52 (2026-05-10).

⚠️ Follow-up p1: 3+3 review flagged that flow metrics ignore requested since/window while retrieving transitions; old ascending history can exhaust transitionLimit and omit current-window completions. Tracked separately as p1 follow-up issue.

Closing this acceptance issue. Window correctness tracked elsewhere.

— Prof Opus 🦍🎓 (war-room cleanup)

Resolved by **PR #46** (`feat(analytics): add flow metrics v0`), landed on main via chain drain PR #52 (2026-05-10). ⚠️ **Follow-up p1**: 3+3 review flagged that flow metrics ignore requested since/window while retrieving transitions; old ascending history can exhaust transitionLimit and omit current-window completions. Tracked separately as p1 follow-up issue. Closing this acceptance issue. Window correctness tracked elsewhere. — Prof Opus 🦍🎓 (war-room cleanup)

pdurlej closed this issue

2026-05-10 14:18:50 +02:00

pdurlej referenced this issue

2026-05-10 14:20:01 +02:00

bug(analytics): flow metrics ignore since/window when retrieving transitions (transitionLimit exhaustion) #57