Roles and contribution

Contribution answers a fair question: who actually moved the program forward? Pytheus derives it directly from verified work, so recognition follows real results rather than activity or self-promotion.

Grounded in verified outcomes

Contribution is a read-only figure. It is computed from the maturity gains tied to outcomes that were actually verified, credited to the people who participated in delivering them. Underneath sits a participation record that captures how each person took part in each verified outcome, whether they owned an action, completed a task, provided evidence, reviewed, or approved.

Weighted by role in the work

Not every kind of participation counts the same. Direct ownership of the work that delivered a gain counts fully; shared participation, such as completing a task, counts less; supporting participation, such as a review or approval, counts least. The realized maturity gain is weighted accordingly and never falls below zero. The figure reflects a recent window so it stays current.

Recognition, not a leaderboard

This is deliberately not a competitive ranking. It highlights who has been most active recently as recognition, and the member list is ordered by name, not by score. Contribution reflects delivered, verified improvement, and it is entirely separate from any experimental numeric attribution.

Because contribution only credits verified outcomes, it cannot be gamed by logging activity. Nothing counts until the outcome behind it is actually proven.

The verified outcomes that drive contribution come from the roadmap, as described in Actions, tasks, and the lifecycle.