Democratic institutions need infrastructure that preserves authority, memory, and accountability.

The fracture

Run any cooperative, community organization, or federation long enough and the same pattern appears.

Governance happens in meetings and minutes. Policy lives in documents nobody reads the same way twice. Membership lives in a spreadsheet or a CRM that was built for a sales team. Accounting lives in a system that has no idea what a decision was. Execution happens because a specific person remembers what they were supposed to do.

Each of these tools is fine in isolation. Together, they produce drift.

Decisions do not reliably become action. Rules do not reliably bind practice. Accountability decays into trust in individual people instead of trust in the institution. And when something goes wrong, there is no path back from the outcome to the decision that was supposed to govern it.

This is not a failure of any one tool. It is the gap between institutional life and the software stack democratic organizations have been forced to use.

Most of the tools we depend on do not answer to us

The deeper problem is that most of the systems we depend on — platforms, employers, infrastructure providers, administrative backends — do not answer to the people who live inside them. They answer to ownership, to management, to capital, or to centralized administration.

Name the stack plainly and the problem becomes clearer: Google Workspace or Microsoft 365 hold documents, mail, and calendars; Loomio holds votes; QuickBooks holds the books; Slack or Teams hold operational coordination; Salesforce, Airtable, or a spreadsheet often stand in for membership. The institution lives across all of them, but none of them carries the institution as a whole.

This is not a conspiracy. It is the default shape of software built for firms and platforms. Democratic institutions are forced to operate inside it, and they pay the translation cost every day, in staff time, in lost history, in weakened accountability, in the quiet conversion of institutional trust into individual trust.

Why better tooling alone does not fix this

It is tempting to believe the answer is a better project management tool, a better voting app, a better accounting package, or tighter integration between them.

It is not.

The problem is not that the tools are individually bad. The problem is that none of them model the institution itself. None of them know what a member is. None of them know what a rule is. None of them know what it means for a decision to bind action. Integrating them only spreads the gap more evenly.

In that sense, the goal is not merely to swap Google for Microsoft, Slack for Teams, or one voting app for another. The goal is to replace the dependency pattern itself with infrastructure that can carry governance, records, obligations, and coordination as institutional facts.

A cooperative running on a stack of generic tools is not running on infrastructure built for cooperatives. It is running on infrastructure built for firms and platforms.

Why this matters beyond convenience

The cost of the fracture is not just operational overhead. It is legitimacy.

Every serious institution runs on a chain that looks something like this: a member has standing, standing confers authority to participate in decisions, decisions produce policy, policy binds action, and the record of what happened becomes the basis for the next round of standing and authority. When that chain is broken — when the rules live in one place, the decision in another, the action in a third, and the record in none of them — the institution is running on trust in individuals, not trust in itself.

That works until it doesn't. It does not scale, it does not federate, and it does not survive the departure of the people who held the loop together in their heads. A democratic institution's authority comes from its ability to show that chain intact. Losing the chain means losing the authority, even if nothing visibly breaks.

What ICN proposes

ICN proposes that the institutional substrate itself should be the software.

Identity, standing, authority, governance, policy, economic life, execution, provenance, and federation should not be scattered across a stack of tools held together by staff discipline. They should be stations in one coherent loop — where members can be recognized, decisions carry into real operational effect, obligations are carried as institutional facts, and the whole history remains legible to the people who live inside it.

1. 01

   Identity
   ↓
2. 02

   Standing
   ↓
3. 03

   Authority
   ↓
4. 04

   Governance
   ↓
5. 05

   Policy
   ↓
6. 06

   Accounting
   ↓
7. 07

   Execution
   ↓
8. 08

   Receipts & Provenance
   ↓
9. 09

   Member Experience

That is not a small claim, and ICN does not pretend the work is done. But the direction is clear, and the gap it addresses is real. How It Works walks each station in plain language; What's Real Now says which stations are strongest today and which are still being built.