A community for developers, researchers, and enterprise AI teams
The community page is not a generic landing page. It connects evidence, implementation, and adoption paths across the RCT ecosystem.
implementation and knowledge exchange
GitHub, Discord, forum
narrative handoff across the resource system
multi-role enterprise path
The primary channels to use based on the work you are doing
Each channel has a distinct role so the community page does not collapse into a generic link directory.
GitHub
Public repositories, implementation examples, issue workflows, and technical discussion for builders.
Discord
Real-time discussion for implementation questions, routing, protocol, and deployment patterns.
Community forum
A place for deeper questions, system design discussion, and conversations that need more context than live chat.
If you need another resource before joining, start in one of these routes
The community works best when connected to clear archive, docs, and evaluation flows.
Enter through research and releases
Best for researchers and architecture teams who want the evidence trail before joining the conversation.
Enter through docs and integration
Best for implementation teams integrating MCP tools or deployment patterns into real systems.
Enter through evaluation and use cases
Best for buyers, operators, and stakeholders who need decision context before trial work begins.
Use community as the operational layer of the resource system
Start in the community to connect with the right people, then continue into docs, research, evaluation, or contact based on your role.