Growth: AI Agent Project Mortality Prediction — Early Warning System to Detect Dying Projects Before Founders Build on Them

[sykp241095]

Problem/Opportunity

AI founders and developers face a critical risk: building their product on top of an agent framework that's about to die.

When a foundational project dies, the consequences are severe:

• Forced migration to a new framework (weeks/months of rework)
• Security vulnerabilities go unpatched
• No support for breaking changes from upstream LLM APIs
• Community knowledge becomes obsolete

Currently, founders discover a project is dying only after it's too late — when releases stop, issues go unanswered, or the repo is archived. We can predict this months in advance using GitHub signals.

Implementation Plan

Phase 1: Signal Collection

Track these leading indicators of project decline:

1. Contributor Churn Rate — % of core contributors who haven't committed in 60/90 days
2. Release Cadence Decay — Time between releases increasing over 3+ versions
3. Issue Response Time Degradation — Median time to first response trending upward
4. PR Merge Rate Decline — % of PRs merged vs. stale over trailing 90 days
5. Competitor Migration Signal — Detect when contributors start committing to competing frameworks
6. Star-to-Issue Ratio Anomaly — Stars plateau while issue volume grows (maintainer overload)

Phase 2: Scoring Model

• Create a Mortality Score (0-100) combining weighted signals
• Threshold bands: 🟢 Healthy (0-30) | 🟡 At-Risk (31-60) | 🔴 Critical (61-100)
• Show trend arrow (↑ worsening, ↓ improving, → stable)

Phase 3: UI Integration

• Add mortality badge to collection pages and individual repo cards
• Build a "Graveyard" page showing projects that crossed the threshold (with post-mortem analysis)
• Optional: Email alerts for watched projects when score crosses thresholds

Phase 4: Validation & Calibration

• Backtest against known dead projects (e.g., early agent frameworks that died in 2023-2024)
• Publish methodology transparency (avoid "black box" criticism)

Why AI Builders Would Care

1. Risk Mitigation — Choosing a framework is a 6-12 month commitment. This reduces catastrophic bet-the-company risks.

2. Competitive Intelligence — If a competitor's framework is dying, that's a market opportunity.

3. Due Diligence for Investors — VCs backing AI startups can assess technology risk in portfolio companies.

4. Migration Planning — Teams can start planning exit strategies before emergency mode.

Estimated Impact

Metric	Estimate
Traffic	+15-20% from founders researching framework choices
Engagement	High time-on-page (risk assessment is serious research)
Retention	Users return to check watched projects weekly
Viral Potential	High — "Project X just crossed into Critical zone" is shareable news
Differentiation	Zero competitors offer this (DB-Engines, SimilarTech, etc. don't predict death)

Technical Notes

• Use existing GitHub API data (no new data sources needed)
• Can start as simple heuristic model, iterate to ML-based prediction
• Integrate with existing "AI Agent Ecosystem Maturity Stage Classifier" but focus on prediction vs. classification
• Consider open-sourcing the scoring model for community trust

Success Metrics

• 500+ projects tracked in first month
• 50+ users setting up watchlist alerts
• At least 1 accurate "prediction" validated within 90 days (project dies after we flagged it)