docs: Add ecosystem directory for community projects#27
docs: Add ecosystem directory for community projects#27MaxSemenchuk wants to merge 2 commits intoregen-network:mainfrom
Conversation
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>
Summary of ChangesHello @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
Changelog
Activity
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
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.
docs/ECOSYSTEM.md
Outdated
|
|
||
| ## 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. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
@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>
Summary
docs/,README.md,CONTRIBUTING.mddocs/ECOSYSTEM.md— a directory of ecosystem projects building on the agentic tokenomics framework, with links from README and CONTRIBUTINGnode scripts/verify.mjs(passes) or docs-only reviewDetails
docs/ECOSYSTEM.mdlists the coordination layer, core stack (linking to STACK_MAP.md), community projects (regen-compute-credits, netnet, regen-heartbeat), and organizations (agent-ecowealth)README.mdgets a new "Ecosystem" section with linkCONTRIBUTING.mdgets a "List Your Project" section + TOC entryTest plan
node scripts/verify.mjspasses🤖 Generated with Claude Code