ICN is shared digital infrastructure for democratic organizations.

A different kind of system

ICN is not an app, a management SaaS, a blockchain, or a DAO platform.

It is infrastructure: the layer underneath institutional life that most democratic organizations have never had. The premise is that membership, authority, rules, records, and coordination should not have to live in separate products owned by somebody else.

Today that layer is improvised. It lives in spreadsheets, chat threads, documents, staff memory, and disconnected tools that were never designed to carry institutional weight. ICN is an attempt to provide a durable alternative.

Today that usually means relying on systems such as Google Workspace or Microsoft 365 for records, Loomio for voting, QuickBooks for accounting, Slack or Teams for coordination, and a CRM or spreadsheet for membership. ICN is not trying to flatter that stack with better integrations. It is trying to reduce the institution's dependence on it.

What ICN models directly

Most software models users and accounts. ICN models institutions.

• Members — people with cryptographic identity and real, provable standing inside the institutions they belong to.
• Scopes — cooperatives, communities, federations, and commons, each modeled as a first-class institutional entity with its own rules, members, and history.
• Authority — not handed down from a platform owner, but derived from the scope's rules and the decisions its members have made under them.
• Governance and policy — proposals, deliberation, and the rules those decisions produce — rules that shape what can happen next.
• Economic life — obligations, treasury with budgets and approvals, mutual-credit positions, patronage settlement, usage-rights. Social accounting denominated in obligations between real parties, not payment rails.
• Execution — the step where an accepted decision turns into a concrete operational effect, so decisions do not die in meeting minutes.
• Receipts and provenance — durable records that trace every outcome back through the rule that shaped it, the decision that authorized it, and the members who held standing.
• Federation — formal agreements, attestations, and cross-institutional clearing between distinct scopes. Coordination without merger.

These are not features layered on top of a generic platform. They are the primitives of the system.

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.

Closing the institutional loop

The defining idea behind ICN is that institutional life should not be scattered across unrelated tools. The loop that matters is specific, and the system is built to carry every station of it. Read the nine stations in order:

1. 01

   Identity Cryptographic identity held by the member — not a platform account.
   ↓
2. 02

   Standing Provable participation inside a scope. The institution can verify it directly.
   ↓
3. 03

   Authority Derived from scope rules and the decisions members have made under them.
   ↓
4. 04

   Governance Proposals, deliberation, and decisions the institution will honor.
   ↓
5. 05

   Policy Shared rules produced by decisions, shaping what can happen next.
   ↓
6. 06

   Accounting Obligations, treasury, patronage, mutual-credit positions — governed social accounting.
   ↓
7. 07

   Execution Where accepted decisions translate into real operational effect.
   ↓
8. 08

   Receipts & Provenance The chain from authority to outcome — durable, auditable institutional memory.
   ↓
9. 09

   Member Experience Where all of the above becomes something a person can see, use, and live in.

↻ The loop closes Every round of standing starts the next. Identity does not begin at 01 again — it is reinforced by the provenance that station 08 produces and the member experience at 09.

That is the loop. ICN exists to close it. Parts of it are already closed today; other parts are still being filled in. See What's Real Now for the direct account of which stations are strongest, where work is focused, and which are still behind.

What ICN is not

• Not a blockchain. ICN is not oriented around tokens, speculation, or trustless global consensus. It is oriented around institutions and their accountability to themselves and each other.
• Not a DAO framework. DAOs typically treat governance as voting over a treasury. ICN treats governance as one part of a much larger institutional substrate.
• Not a SaaS suite. ICN is not a bundle of management tools. It is the layer those tools should sit on top of.
• Not yet complete. ICN has uneven maturity today. See What's Real Now for a direct account.

Why this framing matters

If you treat institutions as user groups on generic software, you get what we already have: governance that cannot bind practice, decisions that do not become action, and accountability that depends on individuals remembering what happened.

If you treat institutions as first-class entities with their own identity, rules, and history, something different becomes possible. That is the bet ICN is making.