MVP Completion: ~87% (Phase 1 features fully implemented) Production Status: Core features complete, Phase 2/3 features partially implemented

• Phase 1 (MVP): ✅ 100% Complete (all 7 features implemented)
• Phase 2: ✅ 60% Complete (teams & merge actions done, notifications & bot filtering partial)
• Phase 3: ⚠️ 33% Complete (health scores done, analytics partial, AI not started)

• 6eb0ad8 - Multitenancy support (Organizations, Teams)
• 1e0452f - Bulk merge reliability improvements
• 72935d2 - Infinite scroll pagination
• f95e2bd - Comprehensive integration tests
• 4378b49 - PAT-based multi-account support

Ampel ("traffic light" in German) is a PR management and repository health monitoring system that provides at-a-glance visibility into pull request status and CI health across multiple Git providers. Designed for developers and teams managing dozens to hundreds of repositories.

Modern development teams face:

• PRs scattered across GitHub, GitLab, and Bitbucket
• No unified view of merge-ready PRs across all repos
• Manual checking of CI status for each repository
• Difficulty identifying blocked or stale PRs at scale
• Time wasted context-switching between provider UIs

A single dashboard showing traffic-light status for all repositories:

• Green: CI passing, approved, ready to merge
• Yellow: CI pending, awaiting review
• Red: CI failed, blocked, needs attention

• Manages 10-50 personal/work repositories
• Wants quick daily check of PR status
• Needs to know which PRs are ready for action

• Oversees team of 5-15 developers
• Monitors team velocity and PR throughput
• Needs aggregate view of team's PR health

• Manages multiple teams, 100+ repositories
• Requires high-level health dashboards
• Needs audit trail and compliance visibility

Status: All Phase 1 features are fully implemented and production-ready.

• Personal Access Token (PAT) authentication for GitHub, GitLab, Bitbucket
• Secure token storage with AES-256-GCM encryption at rest
• Support for self-hosted GitLab/Bitbucket instances
• Implementation: ampel-providers/, handlers/auth.rs, entities/provider_account.rs

• Add/remove repositories to monitor
• Wildcard patterns (e.g., "myorg/*") - backend ready, UI pending
• Repository grouping by provider/team
• Implementation: handlers/repositories.rs, queries/repo_queries.rs

• Grid view: Card per repository with status indicator
• List view: Sortable table of all PRs with infinite scroll
• Real-time status updates via polling
• Implementation: handlers/dashboard.rs, components/dashboard/GridView.tsx, components/dashboard/ListView.tsx

• Green: All checks pass + approved + no conflicts
• Yellow: Checks pending OR awaiting review
• Red: Checks failed OR conflicts OR blocked
• Implementation: ampel-core/models.rs, entities/ci_check.rs

• Configurable poll intervals (1min - 1hr)
• Manual refresh option
• Rate limit aware scheduling
• Implementation: ampel-worker/ with Apalis background jobs

• Filter by: provider, status, author, reviewer, age
• Full-text search on PR title/description
• Saved filter presets
• Implementation: handlers/pr_filters.rs, entities/pr_filter.rs

• Full PR information without leaving Ampel
• CI check details with logs link
• Review status and comments summary
• Implementation: handlers/pull_requests.rs, entities/review.rs

Status: Teams and bulk merge fully implemented. Notifications have backend structure but no sending implementation. Bot filtering partially implemented.

• Create/manage teams within organizations
• Team-specific dashboards and filters
• Member role management (admin, member, viewer)
• Implementation: handlers/teams.rs, entities/team.rs, entities/team_member.rs
• Note: Originally planned for Phase 2, but fully implemented ahead of schedule

• Slack integration for status changes - Backend config ready, no worker sending
• Email digests (daily/weekly summaries) - SMTP settings exist, no sending implementation
• Browser push notifications - Not started
• Implementation: handlers/notifications.rs, entities/notification_preferences.rs
• Missing: Worker jobs to actually send notifications, frontend notification UI

• One-click merge from dashboard
• Batch merge for approved PRs with progress tracking
• Merge strategy selection (squash, merge, rebase)
• Implementation: handlers/bulk_merge.rs, entities/merge_operation.rs, components/MergeDialog.tsx
• Note: Fully implemented with reliability improvements in commit 1e0452f

• Auto-detect Dependabot, Renovate, etc. - Backend detection logic ready
• Separate view for bot PRs - Not implemented in frontend
• Auto-merge rules for bot PRs - Entity/handler exist, no worker execution
• Implementation: handlers/bot_rules.rs, entities/auto_merge_rule.rs
• Missing: Frontend bot view, worker to execute auto-merge rules

Status: Health scores fully implemented. Analytics partially implemented. AI features not started.

• PR cycle time metrics - ✅ Complete
• Review turnaround time - ✅ Complete
• Team velocity trends - ✅ Complete
• Export to CSV/PDF - ❌ Not started
• Implementation: handlers/analytics.rs, entities/pr_metrics.rs
• Missing: Export functionality

• Repository health scoring algorithm (0-100 scale)
• Trend analysis over time with metrics tracking
• Alerting on health degradation - ⚠️ Scoring exists, alert mechanism not implemented
• Implementation: entities/health_score.rs with scoring fields: avg_time_to_merge, avg_review_time, stale_pr_count, failed_check_rate, pr_throughput
• Note: Originally planned for Phase 3, core functionality implemented early

• Smart PR prioritization - Not implemented
• Reviewer recommendations - Not implemented
• Anomaly detection - Not implemented
• Status: No implementation, future roadmap item

• US1: As a user, I can sign up with email/password
• US2: As a user, I can connect my GitHub account using a Personal Access Token
• US3: As a user, I can connect my GitLab account using a Personal Access Token
• US4: As a user, I can connect my Bitbucket account using an App Password
• US5: As a user, I can revoke provider access at any time

• US6: As a user, I can browse my accessible repositories
• US7: As a user, I can add repositories to my watchlist
• US8: As a user, I can use wildcards to add multiple repos
• US9: As a user, I can organize repos into custom groups

• US10: As a user, I see a grid of repos with status colors
• US11: As a user, I can switch between grid and list views
• US12: As a user, I can filter PRs by multiple criteria
• US13: As a user, I can search PRs by title or author
• US14: As a user, I can save filter combinations as presets

• US15: As a user, I can view PR details in a side panel
• US16: As a user, I can see CI check status and logs
• US17: As a user, I can see review comments summary

• US18: As an org admin, I can create teams
• US19: As a team admin, I can add members to my team
• US20: As a team member, I can view team dashboard

┌─────────────────────────────────────────────────────────────┐
│ [Logo] Ampel          [Search...]     [Filter] [View] [👤] │
├─────────────────────────────────────────────────────────────┤
│ Sidebar    │  Main Content Area                             │
│            │                                                │
│ Providers  │  ┌─────┐ ┌─────┐ ┌─────┐ ┌─────┐              │
│ ├ GitHub   │  │ 🟢  │ │ 🟡  │ │ 🔴  │ │ 🟢  │              │
│ ├ GitLab   │  │repo1│ │repo2│ │repo3│ │repo4│              │
│ └ Bitbucket│  │ 2PR │ │ 1PR │ │ 3PR │ │ 0PR │              │
│            │  └─────┘ └─────┘ └─────┘ └─────┘              │
│ Teams      │                                                │
│ ├ Frontend │  ┌─────┐ ┌─────┐ ┌─────┐ ┌─────┐              │
│ └ Backend  │  │ 🟢  │ │ 🟢  │ │ 🟡  │ │ 🟢  │              │
│            │  │repo5│ │repo6│ │repo7│ │repo8│              │
│ Filters    │  │ 1PR │ │ 0PR │ │ 5PR │ │ 2PR │              │
│ [Presets]  │  └─────┘ └─────┘ └─────┘ └─────┘              │
└─────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────┐
│ Status │ Repository      │ PR Title        │ Author │ Age  │
├────────┼─────────────────┼─────────────────┼────────┼──────┤
│   🟢   │ org/repo1       │ Fix login bug   │ alice  │ 2h   │
│   🟡   │ org/repo2       │ Add feature X   │ bob    │ 1d   │
│   🔴   │ org/repo3       │ Update deps     │ bot    │ 3d   │
└─────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────┐
│ PR #123: Fix login bug         [×] │
├─────────────────────────────────────┤
│ Repository: org/repo1               │
│ Author: alice                       │
│ Created: 2 hours ago                │
│ Branch: fix-login → main            │
├─────────────────────────────────────┤
│ Status: 🟢 Ready to merge           │
├─────────────────────────────────────┤
│ CI Checks:                          │
│ ✅ build (2m 15s)                   │
│ ✅ test (5m 32s)                    │
│ ✅ lint (45s)                       │
├─────────────────────────────────────┤
│ Reviews:                            │
│ ✅ bob - Approved                   │
│ 💬 carol - 2 comments               │
├─────────────────────────────────────┤
│ [View on GitHub] [Merge ▼]          │
└─────────────────────────────────────┘

• Dashboard loads in < 2 seconds for 100 repos
• Supports 10,000+ repositories per organization
• Handles 1000 concurrent users

• Personal Access Token (PAT) authentication for all Git providers
• PATs encrypted at rest with AES-256-GCM
• HTTPS only, HSTS enabled
• SOC 2 compliance path

• Horizontal scaling for API servers
• Database read replicas for queries
• CDN for static assets

• 99.9% uptime SLA
• Automated failover
• Data backup every 6 hours

This specification was originally written as a planning document. The actual implementation has exceeded expectations in several areas:

1. Phase 2 Features Implemented Early: Team management (F8) and bulk merge actions (F10) were completed ahead of schedule
2. Phase 3 Features Implemented Early: Health scores (F13) and analytics (F12) were implemented during MVP development
3. Multitenancy Added: Organizations and teams were added in commit 6eb0ad8, enabling true multi-tenant support
4. Infinite Scroll: Added in commit 72935d2, improving UX for large PR lists

Based on the implementation matrix above:

High Priority (Complete Phase 2):

• Notification worker to actually send Slack/email notifications
• Frontend UI for bot filtering
• Worker to execute auto-merge rules for bot PRs

Medium Priority (Complete Phase 3):

• Export functionality (CSV/PDF) for analytics
• Alerting mechanism for health score degradation
• Frontend wildcard pattern UI for repository management

Future Roadmap (Phase 4):

• AI features (smart prioritization, reviewer recommendations, anomaly detection)

What Works Today (Production-Ready):

• Complete multi-provider PR aggregation dashboard
• Traffic light status with CI integration
• Team management and collaboration
• Bulk merge operations with progress tracking
• Health scoring and analytics
• Comprehensive filtering and search

What's Partially Implemented:

• Notifications (config exists, no sending)
• Bot filtering (backend ready, no frontend)
• Export (analytics work, no export format)

This spec now reflects reality over aspirations.