From Formation to Continuity

A conversation about what cooperatives need after they begin, and the ecosystem that lets them materially exist.

2026-05-21, 10 minutes, screen-share, reciprocal. Launch first, ICN second.

Speaker copy (≈45 sec):

"Thanks for making time, McKenzie. Before I share anything else, two quick things.

First, who else is on the call with us today?"

[Wait. Let her introduce whoever is curious.]

"Second, I want to be honest about the shape of this conversation. I want to learn how Launch thinks about the formation workflow, and the bigger ecosystem you and the Worker Place and comp.coop are working toward. I'll share enough of what ICN is trying to be that you can tell me where the map is wrong. But the most useful thing for me today is your map. Sound good?"

[Wait for her green light. Then advance.]

What I understand Launch is solving

Starting a worker co-op is too hard.
Resources are scattered.
State rules vary.
TA capacity is limited.
Groups need the right help at the right time.

Speaker copy (≈40 sec):

"Here's the read I have from Launch's public material. Starting a worker co-op is too hard. Resources are scattered. State rules vary. TA capacity is limited. Groups need the right help at the right time."

[Beat.]

"Does that read feel right from inside Launch, or am I missing something fundamental about the problem you're solving?"

[Listen. Take notes verbatim. If she corrects the framing, use her language for the rest of the call.]

Launch's public shape

Onboarding questions, decision-tree style.
Teams, tasks, comments, documents.
Advisors and service providers.
Secure document portal.
Mobile, print, multilingual access.

Speaker copy (≈25 sec, don't dwell):

"And here's the surface read. Onboarding questions in a decision-tree style. Teams, tasks, comments, documents. Advisors and service providers. Secure document portal. Mobile, print, multilingual."

"That's the outside view. I want to know what the inside view looks like — what states a group actually moves through. Let me ask it as five questions on the next slide."

What I want to learn from you

Where does the workflow begin and end?
What states does a group move through?
What do advisors need to see?
What records matter later?
What should software never touch?

Speaker copy (≈3–4 minutes, mostly listening):

"These are the five things I most want to understand from your side. Where does the workflow begin and end? What states does a group move through? What do advisors need to see? What records matter later? What should software never touch?"

"Take any of them. Start anywhere. I'm here to listen, not to teach Launch back to you."

[Now actually listen. Capture her vocabulary verbatim. This is the most important slide of the meeting. Do not advance until she's done. If she talks a long time here, that is GOOD.]

The seam I'm exploring

Launch helps cooperatives come into being. ICN is the question of what helps cooperatives continue governing, remembering, coordinating, and federating after formation. The point is for a cooperative and solidarity-economy ecosystem to materially exist, not just ideologically exist.

Speaker copy (≈90 sec, then pause):

"Okay, so let me share where ICN is trying to sit. Just the framing, not a sales pitch."

[Read the quote aloud, slowly, with a beat between sentences.]

"Launch helps cooperatives come into being. ICN is the question of what helps cooperatives continue governing, remembering, coordinating, and federating after formation. The point is for a cooperative and solidarity-economy ecosystem to materially exist, not just ideologically exist."

[Beat. Then say this once, citing the Summit material, not ICN's vocabulary.]

"I want to be careful with that word ecosystem, because it's not my framing. The 2025 Summit ran an ecosystem-mapping session as one of its top-rated tracks. The kickoff vision named upstate-downstate bridging, cross-sector parity across worker, consumer, financial, ag, and housing co-ops, regional events between summits, and an NY state employee ownership center. The speaker series that went out under our committee's own name called the next wave 'the infrastructure builders designing the legal, technological, and organizational backbone that lets co-ops scale.' That's the layer ICN is trying to be."

"Does that seam feel real from where you sit?"

[Pause. Do not fill the silence. Let her answer first.]

What the ecosystem needs to remember

Member standing.
Decisions and approvals.
Governance documents.
Advisor and service-provider handoffs.
Patronage and capital-account history.
Inter-cooperative trade, obligations, and federation evidence.
Records future members, boards, CPAs, counsel, or a partner cooperative may need.

Speaker copy (≈60 sec):

"If I'm right about the seam, here's the work that lives in it. Member standing. Decisions and approvals. Governance documents. Advisor and service-provider handoffs. Patronage and capital-account history. Inter-cooperative trade, obligations, and federation evidence. And records future members, boards, CPAs, counsel, or a partner cooperative may need to verify later."

"The pattern: each of these records belongs to a cooperative now, but might need to be verifiable to a partner co-op or federation later. That's the difference between an ecosystem that materially exists and one that's just shared values."

"Of that list, what jumps out as the thing your co-op work most needs and least has?"

[Listen. The patronage-and-capital-account piece is the doorway she opened in her May 1 email. If she names it, slow down.]

ICN in one breath

Standing.
Authority.
Decision.
Obligation.
Receipt.
Evidence.
Review.

Speaker copy (≈40 sec to recite):

"If I had to compress ICN into seven words, it'd be these. Standing. Authority. Decision. Obligation. Receipt. Evidence. Review."

[Beat.]

"Not because every human process should become software. Because some records need to survive turnover, without everyone reconstructing the institution from email, PDFs, and somebody's exhausted memory."

[Move on unless she asks. Do not pitch each word.]

If she asks about any one of them, use these:

Standing — who has the right to act in this context.

How it works: signed records of admission, transition, exit. Cryptographic proof of membership at a moment in time.
Quick: not membership management. Membership evidence. So a new treasurer in 2030 can answer "who actually voted on this in 2027?"

Authority — who can authorize what, under what governance rule.

How it works: expressed in CCL (Cooperative Contract Language). The kernel enforces the constraint without understanding the meaning.
Quick: always reducible to a rule + a role + a threshold. Structural, not personal.

Decision — a choice made under authority, with threshold met.

How it works: links the proposal that triggered it, the votes cast, the threshold reached, the effect authorized.
Quick: a vote is not a decision until the threshold is met AND the result is recorded. The recording IS the decision.

Obligation — a commitment created by a decision.

How it works: obligor, obligee, scope, triggering decision, evidence-of-completion.
Quick: replaces "debt" / "liability" in ICN vocabulary. Advisor agreements, patronage allocations, federation commitments all live here.

Receipt — a verifiable record that an event happened.

How it works: signed, content-addressed, everything attached; verifiable independently of any platform.
Quick: receipts alone do not prove legitimacy. They prove the event. Authority and review are separate.

Evidence — receipts plus context, available later.

How it works: receipts plus the chain (charter, governance rules, prior decisions) needed to interpret them; survives platform migration.
Quick: the difference between "we had a vote" and "we can verify the vote across years and platforms."

Review — anyone can verify the chain.

How it works: cryptographic check of signatures + inspection of the contextual chain to confirm authority was real.
Quick: without review, receipts are files. With review, they are evidence. This is what makes ICN useful as institutional memory.

What ICN is not

Not replacing Launch.
Not replacing TA providers, lawyers, CPAs, or co-op developers.
Not accounting software.
Not financial-intermediary software.
Not production-ready or a pilot ask.

Speaker copy (≈30 sec, short version):

"Quick boundary slide. ICN is not replacing Launch or any of the people who do the human work of forming co-ops. It's not accounting software. It's not a financial-intermediary product. It's not production-ready, and this isn't a pilot ask."

[Move on.]

If she asks directly about wallets, tokens, payments, or crypto, expand:

"No wallet, no token, no payment rail, no speculative crypto frame. ICN uses cryptographic verification as record integrity, not as a casino. If anyone reads 'decentralized' and thinks Web3, they're reading the wrong project."

[Then stop. Don't volunteer more.]

A useful test, if anything here feels real

Pick one fictional or sanitized workflow.
Walk it from formation to governance.
Ask what must survive.
Ask who needs it later.
Ask what should stay outside ICN.

Speaker copy (≈35 sec):

"If anything I've said feels like it might be real, here's what a next step might look like. Not a pilot. Not a commitment."

"Pick one fictional or sanitized workflow. Walk it from formation to governance. Ask what must survive. Ask who needs it later. Ask what should stay outside ICN."

"It's one concrete pattern that either proves the seam or kills it cleanly. Either is useful."

[Don't push. The option is on the table.]

The question for today

Where is this map useful, where is it wrong, and what should I learn from Launch before building anything around this seam?

Speaker copy (≈20 sec, then stop talking):

"The question I came in with is on the screen."

[Read it aloud, slowly.]

"Where is this map useful, where is it wrong, and what should I learn from Launch before building anything around this seam?"

[Then stop. Hand the call to her. The whole meeting comes down to what she says next.]

If she answers with a concrete thing, capture it verbatim. If she answers with another question, follow her. If she says "I need to think," that is also a real answer — propose a follow-up date and end the call cleanly.

For Matt, after the call

[Do not display this slide to McKenzie. If short on time, end at slide 10 and skip this.]

Fill these six buckets within 24 hours of the call, sanitized, into the prep packet's §13 capture grid:

Launch validated — what landed.
Launch rejected — what she said is wrong, overbuilt, or unclear.
New vocabulary — her exact words, verbatim.
Privacy boundary — what she said should never be public or recorded.
Possible tabletop — fictional or sanitized workflow worth rehearsing.
No-go zones — what ICN should never touch in this domain.

Use her exact words for the vocabulary bucket. Do not paraphrase yet.