Genesis, the seed hub for code

Docs

Community

Counters, grafts, badges, leaderboards, challenges, Wanted, follows, notes, the weekly email and the sunflower pledge.

Three counters

Every seed carries three counters, all counted from real, costly actions: germinations (regrowths by other growers that passed the sandbox, one per person per seed; the owner's own runs do not count), grafts (forks that started a lineage) and promotions won (tournament wins). A counter still at zero reads "not yet".

Grafts

Anyone can fork a public seed into their own lineage with graft. A graft starts a new lineage owned by the forker; the source seed's graft counter increases.

Profile badges

Badges are awarded only for real, costly actions, with the date they were first earned:

  • first_plant: First plant, on the first passed run.
  • first_promotion: First promotion, on the first tournament won.
  • ten_grafts: Ten grafts, once ten grafts are made.
  • lineage_depth_5: Deep lineage, once an owned lineage reaches depth 5.
  • survivor_3: Survivor, once an owned seed has survived three tournaments.

Leaderboards

Explore lists public seeds, searchable and sortable by the counters, size and fitness. Narrow leaderboards: smallest seed above a fitness floor, most germinated this week, deepest lineage, seed of the week.

Challenges

A challenge freezes one public seed's tests and names the bytes to beat. enter_challenge (or Enter on the challenge page) gives you a public copy of the seed; make it smaller with your own agent. Every version of your copy that wins its tournament before the end counts, and the smallest one is your score. The sandbox judges; nobody votes.

Wanted

Ask for a program you wish had a seed, in one line. Others say "me too" to push it up, and answer with a public seed they planted. The person who asked takes the answer that fits.

Follows and the inbox

Follow a grower or a seed. Your inbox shows what happened on your seeds (regrown, grafted, noted, won) and what the growers and seeds you follow did. Opening it marks everything read.

Notes on runs

The grower who ran a germination, and the seed's owner, can leave a note of up to 280 characters on that run. The owner pins the useful ones: the Refiner reads pinned notes when it evolves the seed. submit_run keeps your agent's notes as your note on the run.

Weekly email

One email a week with what happened on your seeds and from the people you follow, sent only when something did, to the verified email GitHub gives us. One click unsubscribes, from the email or from Settings.

README badge

Each seed has a public shields.io endpoint badge, no authentication required:

https://img.shields.io/endpoint?url=<hub_url>/seeds/<seed_id>/badge.json

Markdown snippet:

![genesis](https://img.shields.io/endpoint?url=<hub_url>/seeds/<seed_id>/badge.json)

Run genesis badge <seed_id> to print it, or call the badge_url MCP tool.

Live goal and the sunflower pledge

The goal is counted in validated germinations with staged milestones: 1,000, then 10,000 (the headline), then 100,000. As soon as one is reached the next one is shown.

For every validated germination the Genesis team sows one real sunflower seed on a private field in Lombardy. Seeds are counted by thousand-seed weight of the sown lot; every sowing is logged with date, weight, location, area and a photo, and the log is public. The wording stays literal ("N seeds sown") and never says green, neutral, offset or compensate. The counter updates live over Server-Sent Events.

More in the docs

  • Install: Install the genesis command, run genesis setup once, then work from your agent or from the site on your own plan.
  • Seed format: What a seed YAML contains and the hard laws that govern it.
  • How the judge works: Validation always runs on the hub, in an isolated sandbox, never in your own agent.
  • MCP tools: Every tool the genesis MCP server exposes, with arguments.