fork-cohort

Fork activation tracking works by reading GitHub forks, fetching their latest workflow runs, and inspecting aeon.yml to assign activity buckets. It reveals which Aeon instances are actively running by classifying forks into COLD, STALE, ACTIVE, or POWER stages.

A fork activation cohort groups forks by recent run activity to monitor weekly engagement. By maintaining lightweight in-memory state, it computes week-over-week deltas and outputs daily articles documenting cohort distribution, trends, and per-fork workflow run details.

To generate a status report for GitHub organization forks, run the classification process to assign buckets like POWER, ACTIVE, STALE, COLD, or UNREADABLE. It outputs a daily article with actionable insights and maintains state to compute week-over-week deltas for weekly reporting.

Yes, this workflow is applicable to GitHub organizations with Aeon forks. It monitors weekly activation cohorts by reading forks, fetching latest workflow runs, inspecting aeon.yml, and generating daily status reports to surface active Aeon instances.

A limitation of classifying forks by workflow run activity is that forks without readable aeon.yml files are assigned an UNREADABLE bucket. The system also relies on lightweight in-memory state to compute week-over-week deltas, which may not persist across long-term sessions.