ICN is institutional infrastructure for cooperatives and cooperative networks.

The institutional problem you actually face

Most cooperatives operate across a stack of tools that were built for firms, platforms, or administrative convenience, and then stretched to cover democratic life. Membership sits in a CRM or spreadsheet. Governance happens in meetings whose minutes live somewhere separate from the decisions they produced. Rules live in documents that are read inconsistently and interpreted differently depending on who is in the room. Accounting lives in a system that has no idea what was decided. Execution depends on whoever remembered what they were supposed to do.

Concretely, that often means Google Workspace or Microsoft 365 for documents and internal records, Loomio for voting, QuickBooks for accounting, Slack or Teams for day-to-day coordination, and some combination of CRM, Airtable, or spreadsheets for membership and standing.

Each of these tools, in isolation, can be made to work. Together, they produce drift. Decisions do not reliably become action. Rules do not reliably bind practice. Accountability decays into trust in the specific people holding the pieces together in their heads. And when those people leave, burn out, or disagree about what happened, the institution can lose what it knew.

Why generic software is not enough

The underlying problem is that none of those tools model the institution itself. They do not know what a member is in the sense that matters to a cooperative. They do not know what a rule is in the sense that should bind practice. They do not know what it means for a decision to authorize an action. Integrating them only spreads the gap more evenly.

This also means ICN should not be understood as a one-for-one clone of Google, Microsoft, Slack, QuickBooks, or Loomio. The aim is deeper than substitution at the app layer. It is to give the cooperative its own institutional substrate, so those functions no longer depend on a bundle of external systems held together by staff discipline.

What changes when the institutional loop is closed

ICN is built on the claim that the pieces of institutional life should not be scattered across unrelated systems. When the loop closes, a cooperative gets things that are genuinely hard to get today:

• A member's standing is provable — not a row in a CRM, but a cryptographic fact the institution can verify directly.
• A decision made in a meeting has a durable, pointable existence — not as minutes someone wrote up afterward, but as an artifact of the institution itself, tied to the members who held standing in it.
• A rule the membership agreed to is visible at the point where it matters, not buried in a document that gets read once a year.
• Obligations between members or between cooperatives are carried as institutional facts — with treasury, budgets and approvals, patronage settlement, and mutual-credit positions — not entries in a private spreadsheet.
• The chain from what we decided to what actually happened stays intact, so the institution can answer its own members honestly about its own actions.
• Federation with other cooperatives is a first-class mechanism — formal agreements, attestations, and cross-institutional clearing — not something two organizations have to hold together by email and trust in specific staff.
• Shared infrastructure — compute, storage, coordinated work — can be held as a commons with governance, placement, clearing, and dispute resolution built into the same loop, not bolted on after the fact.

None of this replaces the work of running a cooperative. It changes what the work is resting on.

Scope is context of action, not hierarchy. Every ICN action belongs to one or more scopes at once.

1. Commons Shared resources governed by the institutions that use them.
2. Federation How distinct institutions coordinate without merging.
3. Community A group of members with shared rules, purpose, and standing.
4. Cooperative A scoped institution owned and governed by its members.
5. Self The individual member — the identity that holds standing in each scope above.

Read top to bottom: widest shared context down to the most personal. A single decision can touch several scopes at once — that is the point. The receipt it produces is tagged with every scope it passed through.

What is real today

Some of this is already working. The strongest parts of ICN today are provenance and institutional memory — the chain that carries an outcome back through the rule that shaped it, the decision that authorized it, and the members who held standing. Cryptographic identity and membership primitives are in place. The architectural discipline that keeps enforcement and institutional meaning cleanly separated is real and enforced in the codebase.

Execution coverage — how broadly an accepted decision translates into operational effect — is where active development is concentrated. The mechanism exists; the range of decisions it handles is expanding.

Federation (treaties, attestations, cross-institutional clearing) and commons/compute (shared infrastructure with placement, clearing, and dispute resolution) have serious implementation behind them. Economic semantics — treasury, budgets, patronage settlement, usage-rights accounting — are real, with cross-scope integration still being completed.

The member-facing experience is the part of the system still furthest from what it will eventually be. The capabilities underneath are real; the unified interface for ordinary members is still being built. If you tried to adopt ICN this month, that gap is what you would feel most.

The full account, with bounded maturity language for every subsystem, is at What's Real Now.

What is not ready to overclaim

We want to be direct about what ICN is not, today:

• It is not a product you can buy, install, and hand to your membership this week. A cooperative adopting ICN right now is working with engineering help, not clicking through a polished onboarding flow.
• It is not a managed platform with a vendor behind a support contract. ICN is open, cooperative infrastructure, with the usual tradeoffs of early-stage open infrastructure.
• It is not a complete federation fabric. Federation is real, but not everything a federation would want to do across its members is finished.
• It is not a replacement for the governance your cooperative already does. It is the layer underneath — the layer that can remember, carry, and make legible what your governance decides.

How to think about timing and adoption

If you are running a cooperative today, there are a few honest ways to relate to ICN.

The first is observation: following the work, understanding the direction, being in a position to evaluate it as the surfaces mature. This is the right relationship for most cooperatives right now.

The second is early collaboration: working with the project in depth, with real engineering involvement, as a cooperative or federation willing to be part of how the substrate gets shaped. This is the right relationship for institutions that have the capacity and the interest, and who understand they are helping build the thing, not buying it finished.

The third is contribution of expertise: bringing the institutional knowledge of how real cooperatives actually run into the design of the substrate. ICN needs to be informed by the institutions it is meant to serve.

What we would ask you not to do is treat ICN as a SaaS product to pilot next quarter. That is not where the work stands today.

How to engage right now

The practical next step depends on what kind of relationship you want with the project. These are the current real paths:

1. Evaluate first. Read What's Real Now and confirm that the current maturity is compatible with your timing.
2. Bring a concrete institutional case. Open a GitHub Discussion that describes the governance, accounting, coordination, or federation problem your current stack does not carry well.
3. If you only want to support the work without implying a vendor relationship, use the GitHub Sponsors rail on Get Involved.

• Track the work before you commit institutional energy. Start with What's Real Now, then use Community to follow the repository and discussions.
• Bring institutional patterns, not just product requests. If your cooperative, federation, or aligned project has a real governance, accounting, or coordination problem that the current stack cannot carry cleanly, use Get Involved for the current collaboration path.
• Assume early collaboration is engineering-heavy. There is no formal pilot program or managed onboarding track yet. Institutions engaging in depth are helping shape the substrate directly.
• If you want to support the work financially without implying a vendor relationship, the live path today is the GitHub Sponsors rail surfaced on Get Involved.

This is about enhancing human institutions, not automating them away

The work of running a cooperative — deliberation, interpretation, care, negotiation, political judgment, the mediation of disagreement, the responsibility for what the institution does in the world — is human work. It is hard, and the hardness is not a defect.

What ICN is trying to change is the fragility of the glue that holds institutional coherence together. Better memory. Better continuity. Better accountability. Better legibility. Better collective capacity across organizations. So that the attention of members and staff can go to the work that actually requires human judgment.