Where the work is visible, discussable, and open to contribution.
ICN is built in the open. This page collects the working surfaces: how to choose a contribution path, where to discuss design and institutional questions, where to file issues, and where financial support actually goes today. Repository counts below are generated from the repo at build time.
Truth anchor
Read the current maturity account before you assume what ICN can already carry for contributors or institutions.
Get Involved
The route map for developers, non-technical contributors, institutions, and sponsors.
Star on GitHub
Show your support and stay updated. 1 branches, 0 merged PRs.
Open or review issues
Use issues for bugs, scoped implementation work, documentation gaps, and concrete follow-up tasks.
Discussions
Use discussions for design questions, governance patterns, institutional use cases, and broader project conversation.
Contributing Guide
Architectural guardrails, regulatory invariants, and what a good ICN pull request must respect.
Developer getting started
Use the repo quickstart when you want to build the workspace, run the checks, and contribute without getting lost.
Documentation
827+ documents covering architecture, APIs, guides, economics, and governance.
GitHub Sponsors
The live financial-support rail today. Sponsor the organization-level work sustaining the substrate.
Discord
The live real-time chat surface today. Join the ICN Discord server for coordination, contributor questions, and project discussion.
Good First Issues
Labeled, scoped, and documented. If you want to contribute code but don't know where to start, start here.
Announcements
Sprint summaries, release notes, and major milestones. Subscribe to the Announcements discussion category on GitHub.
Contributing Principles
Interfaces First
Design the interface before the implementation. Every public API should be driven by use cases from cooperative governance, economics, or federation scenarios.
No Drive-By Refactors
Each PR touches one concern. If you notice something that needs refactoring while working on a feature, open a separate issue.
The Meaning Firewall
The kernel must never understand the semantic meaning of what it processes. If domain logic leaks into kernel crates, the architecture is broken.
Architectural Guardrails
All changes must respect crate boundaries, the app/kernel separation, and the constraint engine model. See CONTRIBUTING.md for details.