ARCHIVED 2026-07-13. This is the 2025-era "Institution-in-a-Box" vision, preserved unchanged below the marker. It described a municipal-OS product bundle, a "mana"-metered compute economy, and a philosophy-first adoption wedge — all retired. The current vision lives at the repository root: `VISION.md`. Retirement context: 2026-07-13 ecosystem audit; current doctrine: docs/genesis.md, docs/architecture/KERNEL_APP_SEPARATION.md.


Vision: Institution-in-a-Box

"Every human group can run its own institution. On their hardware. With verifiable identity, consent, and auditability."

You don’t “pivot” from what we have into the vision. You route it.

We are keeping the core invariant (sovereign nodes + trust-gated coordination) and deliberately growing the interfaces that make it feel like “the internet finally grew up.”

The Promise

"Spin up a community. Give it rules. Give it money flows. Give it governance. Make it interoperable. Make it accountable."

That’s the north star.

1. Institution Primitives (The Kernel)

We expose 4 “institution primitives” cleanly:

  1. Identity & Membership: Who is in/out, what roles exist, verification, revocation.
  2. Rules & Governance: Proposals, deliberation, voting, constitutional constraints.
  3. Economics: Budgets, mutual credit, accounts, spending limits, audits.
  4. Interoperation: Federation agreements for trade, sharing, and arbitration.

2. The Product: Institution-in-a-Box

The first real product is a boring, powerful bundle: a municipal operating system starter kit.

  • One-click “New Coop / New Community”
  • Default charter templates
  • Membership onboarding
  • Treasury ledger
  • Proposal + vote loop
  • Dashboard: “What decisions exist, what money moved, who authorized it”

3. The Compute Commons (The Consequence)

We don't pitch "a compute commons." We pitch capability. Compute is a paid-in-kind resource.

  • Communities contribute compute/storage/bandwidth.
  • They earn internal credit.
  • They spend it on shared services (search, hosting) or federation-wide projects.

Compute becomes the “mana meter” behind cooperation.

4. Federation Agreements (The Bridge)

The Federation Agreement defines trust thresholds, dispute resolution, cross-ledger clearing, and data sharing between groups. This turns isolated islands into a civilizational mesh.

Roadmap: From Vision to Inevitability

  1. Stage A: Institutions (Institution-in-a-Box, Charters, Treasury)
  2. Stage B: Federation (Agreements, Cross-group Trust, Clearing)
  3. Stage C: Commons (Resource Contribution, Shared Services)
  4. Stage D: Civilization Tools (Municipal Governance, Public Infrastructure)

The Adoption Wedge

Our adoption wedge must deliver value before philosophy:

  • Group purchasing
  • Mutual aid funds
  • Community grants
  • Shared services

Governance Law: The Meaning Firewall

  • Kernel enforces mechanisms (identity, trust, audit).
  • Apps define meaning (what is a “member”, “vote”, “budget”).

Turn what you have into the vision by productizing “institution primitives,” shipping Institution-in-a-Box, then scaling via Federation Agreements until the compute commons emerges as the resource layer behind cooperation.