analytics/event-foundation-v0 #21

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

Parent: #2
Wave: 4 - Analytics Foundation
Depends on: #20 when historical accuracy is needed

Summary

Create a read-only transition history foundation from card activity events.

Scope

  • Build read model for card/list transition history using activity events.
  • Preserve public IDs for stable joins: card, board, fromList, toList.
  • Support filters by board, date range, actor, source, and card.
  • Keep this read-only and event-derived.

Non-goals

  • No metrics dashboard yet.
  • No mutation or correction of history.
  • No warehouse/BI stack.

Acceptance Criteria

  • A card transition timeline can be queried by public card ID.
  • Board-level transition history supports date filtering.
  • Create events include initial toList* data where available.
  • Move events preserve from/to list names and public IDs.

Tests / Smoke

  • Repository/API tests for transition extraction.
  • Fixture covering create into Captured and move Captured -> Doing.
  • Regression against agent audit metadata fields.

Rollback

Disable transition-history endpoint/read model; no data changes.

Owner Gates

No production gate unless DB migrations or data backfill are introduced.

Parent: #2 Wave: 4 - Analytics Foundation Depends on: #20 when historical accuracy is needed ## Summary Create a read-only transition history foundation from card activity events. ## Scope - Build read model for card/list transition history using activity events. - Preserve public IDs for stable joins: card, board, fromList, toList. - Support filters by board, date range, actor, source, and card. - Keep this read-only and event-derived. ## Non-goals - No metrics dashboard yet. - No mutation or correction of history. - No warehouse/BI stack. ## Acceptance Criteria - A card transition timeline can be queried by public card ID. - Board-level transition history supports date filtering. - Create events include initial `toList*` data where available. - Move events preserve from/to list names and public IDs. ## Tests / Smoke - Repository/API tests for transition extraction. - Fixture covering create into Captured and move Captured -> Doing. - Regression against agent audit metadata fields. ## Rollback Disable transition-history endpoint/read model; no data changes. ## Owner Gates No production gate unless DB migrations or data backfill are introduced.
Owner

Resolved by PR #45 (feat(analytics): add transition history read path), landed on main via chain drain PR #52 (2026-05-10).

Closing.

— Prof Opus 🦍🎓 (war-room cleanup)

Resolved by **PR #45** (`feat(analytics): add transition history read path`), landed on main via chain drain PR #52 (2026-05-10). Closing. — Prof Opus 🦍🎓 (war-room cleanup)
Sign in to join this conversation.
No labels
3plus3-followup
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
analytics
api
cockpit
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
docs
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
gemini-flash
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
leviathan
mcp
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
ops
priority:p0
priority:p1
priority:p2
priority:p3
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
safety
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
scout
security
size/large
size/medium
size/small
size/tiny
size/unknown
small-task
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tests
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
ui
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/kan-ductor#21
No description provided.