Skip to content

Team & Execution

Measures whether the team reliably ships: live product plus ongoing feature releases.

Methodology

What We Look For

The Team & Execution signal validates that the team is actively building and shipping product improvements.

Evaluation Criteria:

  • Consistent commits on GitHub
  • Regular releases and version tags
  • Public changelog or "Whats New" updates
  • Active development on the default branch

Scoring Factors:

  • High commit frequency indicates active development
  • Multiple active contributors shows team collaboration
  • Regular releases demonstrate shipping discipline
  • Quality releases (not just version bumps) show real progress

Data Sources

Source TypeExamples
PrimaryGitHub releases/tags/commit history, public changelog
SecondaryBlog/Mirror release posts, Discord/Telegram announcements

Verification Process

Guardians evaluate:

  • Commit history over 30 and 90 day windows
  • Number and quality of releases
  • Substance of changes (not just dependency updates)
  • Consistency of shipping rhythm

Guide

Finding Information

Step 1: Identify Your GitHub Repository

Ensure your project has:

  • Public GitHub repository or organization
  • Active commit history
  • Clear release tags or changelog

Step 2: Review Recent Activity

Check the following metrics:

  • Commits in last 30 days
  • Unique contributors in last 30 days
  • Releases in last 90 days
  • Quality of release notes

Step 3: Document Your Shipping Cadence

Gather evidence of consistent execution:

  • Link to GitHub commit history
  • Link to releases page
  • Link to public changelog (if available)
  • Blog posts or announcements about releases

Submitting Evidence

When submitting execution information:

  1. GitHub Repository:

    • URL to main repository
    • Organization name (if applicable)
  2. Commit Evidence:

    • Link to commit history
    • Note any special circumstances (e.g., private repos with periodic public syncs)
  3. Release Evidence:

    • Link to releases page
    • Link to changelog
    • Recent release announcement URLs
  4. Additional Evidence:

    • Blog posts about feature launches
    • Social media announcements
    • Community updates in Discord/Telegram

Growing crypto's GDP by automating treasury allocations to builders creating real value.