ICN works by connecting the parts of institutional life that are usually split apart.
In most cooperatives, communities, and federations today, the pieces of institutional life live in different systems that don't know about each other. ICN is built on the premise that this fragmentation is not a fact of nature.
Decision, action, and proof in one place
ICN is meant to keep membership, governance, economic life, execution, and institutional memory from fragmenting across separate tools and separate authorities.
Your institution becomes legible to itself
A member should be able to see what was decided, why it was legitimate, what happened next, and how that connects to the wider network their institution belongs to.
The same institution can hold membership, governance, shared rules, economic coordination, execution, provenance, and federation as one coherent substrate — a single underlying layer on which institutional life runs — rather than as seven disconnected systems that staff have to reconcile by hand.
This page walks through the pieces of that substrate one at a time, and then shows how they close a single loop.
01 · 02Identity and membership strong today
Every person, cooperative, community, and federation in ICN has a cryptographic identity they control directly. A member is not an account on a platform. They are a participant with their own keys and their own history, recognized by the institutions they belong to because those institutions can verify their standing directly.
This is what "self-sovereign identity" means in the ICN sense: not independence from institutions, but the ability to be a provable participant inside them.
ScopeScopes and institutions strong today
ICN models cooperatives, communities, and federations as scopes: real institutional entities with their own rules, their own members, their own history, and their own boundaries. A scope is not a tenant on someone else's platform. It is a distinct institution the substrate knows about directly.
Scopes are contexts of action, not levels of hierarchy. When a member acts, they are always acting inside one or more scopes at once. Every decision, every rule, every obligation, and every receipt belongs to its scopes.
Scope is context of action, not hierarchy. Every ICN action belongs to one or more scopes at once.
- Commons Shared resources governed by the institutions that use them.
- Federation How distinct institutions coordinate without merging.
- Community A group of members with shared rules, purpose, and standing.
- Cooperative A scoped institution owned and governed by its members.
- 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.
03 · 04Authority and governance strong today
Governance in ICN is the process by which members of a scope make decisions that the institution will honor. Proposals are created, deliberated on, decided, and recorded. The decisions produce durable artifacts: not just vote tallies, but records that can be pointed to later.
ICN does not govern. Members govern. ICN is the layer that makes the record of their governance durable — that holds the proposal, the deliberation, the decision, and the link between the decision and what happens afterward.
05Policy — rules that bind practice advancing now
Decisions, once made, produce rules. Rules are what govern practice afterward: who can do what, under what conditions, within what limits, with what approvals.
ICN's ambition is that a rule produced by a decision should actually bind the practice that follows — not by removing human interpretation, but by making the rule legible at the point where it matters. The mechanisms that let rules bind practice are under active development and are not yet complete.
06Accounting — governed social accounting advancing now
Economics in ICN is not commerce. It is not primarily about exchange, pricing, or markets. It is about how institutions carry obligations between real parties — who has contributed what, who owes what to whom, how resources are allocated, how budgets are approved, how surpluses are stewarded, and how reciprocity is recorded.
The vocabulary is concrete: obligations, treasury with budgets and approvals, patronage settlement, mutual-credit positions, progressive credit limits, and usage-rights accounting. The accounting is relational, denominated in obligations between named parties, not in a tradable asset. That choice is deliberate — it keeps the economic layer tied to institutional rules rather than drifting into speculation or payment-rail framing.
07Execution and operational effect advancing now
A decision that never touches practice is not really a decision. The hardest problem in institutional software — the one most systems quietly punt on — is execution: the step where an accepted decision turns into a concrete operational effect.
ICN has a mechanism that carries accepted decisions into operational effect. Some types of decisions are already fully wired; others are being added. Expanding that coverage is where active work is concentrated. What's Real Now describes the current state in detail.
08Receipts, provenance, and auditability strong today
When something happens in ICN — a proposal accepted, a rule applied, an obligation settled, an action taken under authorization — the substrate produces a durable record of it. Those records are receipts in the strict sense: evidence that a specific thing happened under specific rules with specific standing.
Provenance is the chain those receipts form. You can follow a particular outcome back to the decision that authorized it, to the rule that shaped it, to the members who had standing in the decision. This is where the substrate is strongest, and it is the anchor the rest of the system is built around.
Every ICN action leaves a trail. The trail is not a log file — it is the chain by which a decision becomes an institutional fact that can be walked back to the authority that produced it.
- Proposal A member or scope proposes an action.
- Decision The scope decides under its rules. The decision grants authorization.
- Execution The authorized action becomes operational effect.
- Effect The effect is recorded — obligations, allocations, state.
- Receipt A durable receipt ties the effect back to the authority that produced it.
Proof flows forward The receipt at step 05 is not the end. It becomes part of the record that confers standing and authority for the next round of decisions. Institutional memory is how ICN ties one action to the next.
Cross-scopeFederation real but maturing
No cooperative is an island. Federation in ICN is the layer that lets scopes recognize each other, enter formal agreements, exchange attestations, and settle obligations across their boundaries — without being collapsed into a single organization.
The principle is that federation strengthens its member institutions rather than dissolving them. A cooperative in a federation is still a cooperative: its own governance, rules, members, and history. The federation is an additional scope that its member institutions participate in, with its own governance and its own agreements — not a merger that erases what it contains.
Federation is real. Serious implementation exists: treaty-grade agreements, attestations, typed inter-institutional channels, and cross-scope clearing. At the same time, the public-facing surfaces that would let an outside reader see federation clearly are still being completed, and some integrations remain partial.
Shared scopeCommons and compute real but maturing
Some things institutions need to do cannot be held by a single organization. Shared resources — compute capacity, storage, coordinated work, infrastructure — need to be held in common across members of a network, with rules that are accountable to all of them. Commons and compute is the name ICN uses for this part of the substrate: shared infrastructure participating in the same institutional loop as governance and accounting.
In concrete terms, the implementation includes trust-aware task placement, cross-participant clearing, checkpointing, and dispute resolution — federation-aware where it needs to be. This is one of the areas where ICN's implementation is meaningfully ahead of its public-facing explanation. The work is serious; the surfaces that would let an outsider see and evaluate it are still being built.
09Member-facing experience behind the system
All of the pieces above are useless if a member cannot actually experience the institution through them. The member-facing surface of ICN is where identity, membership, governance, rules, accounting, receipts, and federation come together into something a person can see and use.
This is an area where the substrate is ahead of the surface. The capabilities underneath are real and in many places strong. The interface through which ordinary members interact with those capabilities is still being built out.
What does it look like to inhabit ICN as a member? This concept shows how identity, governance, accounting, and provenance come together as a single coherent surface — the kind of experience ICN is designed to produce.
Self — your cryptographic identity
Inside Brightworks Collective (cooperative)
Inside Northeast Worker Federation (federation)
Recognized member · Brightworks Collective
Mutual-credit position inside Brightworks
- Contributions recorded
- 142 hours
- Allocations drawn
- 38 hours
- Open obligations
- 2 outstanding
- Patronage (Q3)
- pending approval
Proposal: Extend the commons compute pool cap for the next quarter
- #482 Patronage settlement Q3 — scope: Cooperative stamped 2024-10-31
- #481 Shared room booking approved — scope: Community stamped 2024-10-28
- #479 Federation cross-clearing complete — scope: Federation stamped 2024-10-24
What we are building toward This is an illustration of how governance, economics, scope, and provenance could come together as a coherent member surface. The capabilities beneath each panel are real; the unified interface that ties them together is still being built.
Closing the loop
The point of describing the pieces one at a time is that they are not actually separate. ICN is built on the claim that institutional life breaks down when its pieces are scattered, and works when they are held together.
- Identity belongs to the member — cryptographic, self-held, verifiable.
- Standing inside a scope is not administrative metadata; it is a provable fact about who the member is in this institution.
- Authority flows from the scope's rules and the decisions its members have made under them — not from a platform owner.
- Governance is how members make decisions that the institution will honor.
- Policy is what those decisions produce: rules that shape what can happen next.
- Execution is where accepted decisions translate into operational effect — through obligations, allocations, settlements, commons actions, or federation clearing.
- Receipts and provenance carry the chain from authority to outcome, and feed back into the record the institution runs on.
- Federation lets scopes coordinate across their boundaries without dissolving into each other.
- The member-facing experience is where all of this becomes something a person can actually see, use, and live inside — one institution, not seven tools.
That is the loop ICN is trying to close. Parts of it are already closed today. Other parts are still being filled in.
Why this enhances human institutions rather than replacing them
Everything above is easy to misread as a claim that software can run an institution. It cannot, and ICN is not designed to pretend otherwise.
People still deliberate. People still govern. People still interpret rules, negotiate edge cases, and make calls about what the institution should do when reality does not match what was written down. People still do the work of caring about each other, mediating disputes, and holding each other accountable.
What ICN changes is the fragility of the glue. Most institutions today hold themselves together through individual memory, staff discretion, informal trust, and scattered tools that only a few people fully understand. That glue works until the people holding it burn out, leave, or disagree about what happened.
ICN is built to reduce how much institutional coherence depends on that kind of fragile glue. Better memory. Better continuity. Better accountability. Better legibility. Better collective capacity across organizations. The system holds what the institution has written down so that the people inside it can spend their attention on the work that actually requires human judgment.
What this page does not mean
- ICN does not replace people with software. Deliberation, interpretation, and care remain human.
- ICN does not eliminate politics. Disagreement, negotiation, and contested judgment are still human work.
- ICN does not make institutions automatically fair. A legible rule can still be a bad rule.
- ICN does not collapse all institutions into one model. Scopes are distinct; federations do not erase their members.
- ICN does not require blind faith in external authorities. Sovereignty in the ICN sense is operational — a member can verify their own standing.