Skip to content

docs: Add ecosystem directory for community projects#27

Open
MaxSemenchuk wants to merge 2 commits intoregen-network:mainfrom
MaxSemenchuk:docs/ecosystem-directory
Open

docs: Add ecosystem directory for community projects#27
MaxSemenchuk wants to merge 2 commits intoregen-network:mainfrom
MaxSemenchuk:docs/ecosystem-directory

Conversation

@MaxSemenchuk
Copy link

Summary

  • Lands in: docs/, README.md, CONTRIBUTING.md
  • Changes: Add docs/ECOSYSTEM.md — a directory of ecosystem projects building on the agentic tokenomics framework, with links from README and CONTRIBUTING
  • Validate: node scripts/verify.mjs (passes) or docs-only review

Details

  • New docs/ECOSYSTEM.md lists the coordination layer, core stack (linking to STACK_MAP.md), community projects (regen-compute-credits, netnet, regen-heartbeat), and organizations (agent-ecowealth)
  • Includes "List Your Project" instructions so others can add their repos via PR
  • README.md gets a new "Ecosystem" section with link
  • CONTRIBUTING.md gets a "List Your Project" section + TOC entry

Test plan

  • node scripts/verify.mjs passes
  • All GitHub links in ECOSYSTEM.md resolve correctly
  • STACK_MAP.md relative link works from ECOSYSTEM.md

🤖 Generated with Claude Code

List related repos (regen-compute-credits, netnet, regen-heartbeat, etc.)
so contributors know who's building on the framework and can add their own.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @MaxSemenchuk, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request establishes a dedicated ecosystem directory within the documentation, centralizing information about projects and organizations leveraging the agentic tokenomics framework. It enhances discoverability for community-built solutions and streamlines the process for new projects to be listed, thereby fostering community engagement and collaboration around the framework.

Highlights

  • New Ecosystem Directory: Introduced docs/ECOSYSTEM.md to centralize information about projects building on the agentic tokenomics framework, including core stack, community projects, and organizations.
  • Documentation Discoverability: README.md now includes an "Ecosystem" section linking to the new directory, and CONTRIBUTING.md has a new "List Your Project" section and a corresponding table of contents entry to guide community contributions.
  • Project Submission Guidelines: The new ECOSYSTEM.md file provides clear instructions for community members to submit their projects via pull requests, fostering broader participation.
Changelog
  • CONTRIBUTING.md
    • Added "List Your Project" to the table of contents.
    • Appended a new section detailing how to list a project in the ecosystem directory.
  • README.md
    • Inserted an "Ecosystem" section with a link to the new docs/ECOSYSTEM.md file.
  • docs/ECOSYSTEM.md
    • Created a new document outlining the coordination layer, core stack, community projects, and organizations related to the agentic tokenomics framework.
    • Included instructions for adding new projects to the directory.
Activity
  • No specific human activity (comments, reviews, or progress updates) has been recorded for this pull request since its creation.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request effectively adds an ecosystem directory to the documentation, providing a clear path for community members to list their projects and understand the core stack. The cross-linking between the README, CONTRIBUTING guide, and the new ECOSYSTEM.md is well-implemented. I've noted a small numerical discrepancy in the core stack description that should be corrected for clarity.


## Core Stack

The core development stack spans four repositories with defined data flows and ownership boundaries. See [`architecture/STACK_MAP.md`](architecture/STACK_MAP.md) for the full diagram and routing guide.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The text states that the core development stack spans four repositories, but only three are listed in the bullet points below. If the coordination layer (agentic-tokenomics) is intended to be the fourth, it might be clearer to explicitly state that or adjust the count to 'three' to match the immediate list.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MaxSemenchuk can you clarify and add the coordination layer if you mean that, or the other repo that might be missing ?

Clarify that the core stack is this repo plus three others,
not "four repositories" (which didn't match the three listed).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants