Launch + ICN — Conversation Companion

Companion to the screen deck. Same structure, with definitions, examples, and ready answers for what McKenzie might ask.

Use this during the call when she asks "what do you mean by X?" The deck carries the conversation. This document carries the answers.

Read time end-to-end: ~7 minutes. Reference-during-call: instant — keyed slide-by-slide.

How to use this document

• Section numbers match deck slides. §2 = Slide 2, §5 = Slide 5, etc.
• Each section has the same shape: what's on the screen → plain-English definition → how it works → concrete example → boundary (what it does not mean).
• §11–§13 are reference material: FAQ, glossary, boundary reminders.
• If she asks a question and you don't know where the answer is, check the FAQ first (§11), then the glossary (§12).

Posture

Learn Launch's map first. Share ICN only as a possible continuity layer. Ask where the map is wrong.

This is a reciprocal conversation, not a presentation. McKenzie reached out on May 1 wanting to learn more about ICN and share more about Launch. Both halves matter. She has direct co-op development practice through The Worker Place (governance documents, decision-making, membership, conflict resolution, bylaw change), runs Launch with comp.coop, and ran the 2025 Summit's platform-coops session. Assume domain expertise. Do not teach her field back to her.

Live priority she surfaced (May 1): decision-making, member standing, patronage, and internal capital-account records. Lead with those nouns. The ICN-side translation ("institutional memory," "settlement," etc.) only enters if she reaches for it first.

§1 — From Formation to Continuity (deck slide 1)

What's on screen: title + subtitle + meta.

Frame in one sentence: A conversation about what cooperatives need after they begin, and the ecosystem that lets them materially exist.

What "from formation to continuity" actually means: Launch helps a group become a cooperative. ICN is the question of what helps that cooperative keep being one across founder rotation, advisor turnover, fiscal-year close, member exits, federation with other co-ops, and platform migrations. Formation is a moment. Continuity is the work after.

Example: A worker co-op forms via Launch in 2026. Three founders leave by 2028. The new board needs to know: who has standing, what was decided when, what patronage cycle is mid-flight, what obligations were accepted to advisors. Continuity is whether those answers survive.

§2 — What I understand Launch is solving (deck slide 2)

On screen:

• 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.

Why this matters: This is the read from Launch's public material. It's not me telling Launch what Launch does; it's me showing I did the reading so she can correct me.

What "TA" means: Technical assistance — the broader term for the lawyers, CPAs, co-op developers, bookkeepers, peer advisors, and incubator staff who help groups form cooperatives. Launch's stated goal is to reduce TA bottlenecks without replacing TA providers.

What "state rules vary" means concretely: No single federal cooperative policy in the U.S. New York incorporates worker co-ops differently than California, which differs from Colorado. Tax treatment of patronage refunds varies by state. ESOP-adjacent structures differ. A platform that helps people form co-ops has to navigate ~50 different legal landscapes.

The "right help at the right time" framing: Launch's onboarding is a decision-tree — it prompts founders toward the right service-provider conversation when the moment is ripe, instead of dumping a pile of PDFs at intake.

Boundary: This list is Launch's problem statement, not ICN's. ICN does not solve formation. ICN sits one layer below, in the records and governance work that happens after formation.

§3 — Launch's public shape (deck slide 3)

On screen:

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

Each feature, briefly:

• Decision-tree onboarding: branching questions that route a founding group toward the right co-op model, legal structure, and resource set for their situation.
• Teams, tasks, comments, documents: co-founder workspace — assign work, comment on steps, share drafts, track decisions.
• Advisors and service providers: a surface where lawyers, CPAs, co-op developers, and TA providers can be brought into a founding group's process at the right moment, with the right context.
• Secure document portal: governance documents, financials, and operating drafts in a single place with change history.
• Accessibility: easy-to-read language, graphics/multimedia, mobile-optimized, print options, English + Spanish with room to expand.

Two user groups Launch serves:

1. Co-op founders (the people forming the co-op).
2. Advisors / service providers (the lawyers, CPAs, co-op developers organizing client work and connecting to potential clients).

Boundary: Don't dwell on this slide. It's there to signal "I did the reading." The next slide is the real ask.

§4 — What I want to learn from you (deck slide 4)

On screen:

• 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?

Why each question matters:

• Where does the workflow begin and end? Tells me whether Launch's scope is "intake to incorporation" or "intake to fully-operating co-op." Different answer changes everything downstream.
• What states does a group move through? This is the lifecycle question. A "state" might be: prospective → forming → bylaws drafted → incorporated → operating → first patronage cycle. Each state has different record requirements.
• What do advisors need to see? Tells me whether Launch's advisor surface is read-mostly (advisors browse) or write-mostly (advisors generate work product inside Launch). Tells me whether ICN's "evidence" layer would be useful or redundant.
• What records matter later? This is the seam question. Most records Launch generates are transient (intake forms, drafts, comments). Some records become institutional facts that have to survive every handoff that follows.
• What should software never touch? The most important question. There are things human process must own — care work, conflict resolution, relationship trust, mission interpretation. The wrong answer breaks the co-op.

If only one of these lands: the records-that-matter-later question and the never-touch question are the two that surface the real seam.

Boundary: This is the listening slide. Do not narrate ICN here. Capture her vocabulary verbatim and use her words for the rest of the call.

§5 — The seam I'm exploring (deck slide 5)

On screen, the anchor sentence (read aloud, slowly):

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.

Why "materially exist, not just ideologically exist" is the load-bearing phrase:

The cooperative movement is ~180 years old. It has a corpus (Rochdale Principles, ICA framework, Mondragon experience, 70-year-old worker cooperatives, credit unions, food co-ops, housing cooperatives, community land trusts, mutual aid networks, the solidarity economy). It exists ideologically — as a shared set of values, principles, histories, and identities. What it does not yet have is the shared infrastructure to coordinate as an ecosystem in the way capitalist enterprises coordinate via contracts, markets, and money. That gap is what "materially exist" is pointing at.

The Summit-evidence chain (cite these, not ICN vocabulary):

• The 2025 Summit ran an ecosystem-mapping session as one of its top-rated tracks (per the Lessons Learned doc).
• McKenzie's kickoff vision (12/4/2024): "upstate / downstate connections, bridge the movement for state action," "build cooperative power across the state," "Equity Agenda work on creating an employee ownership center in NYS."
• Recurring asks from the Lessons Learned synthesis: cross-sector parity (worker, consumer, financial, ag, housing), regional events between annual summits, a statewide directory of co-ops, a shared marketing identity, an NY state employee ownership center.
• The committee's own 2025 speaker-announcement series, Part 1, teased Part 2 as: "the infrastructure builders designing the legal, technological, and organizational backbone that lets co-ops scale."
• 2025 was the UN International Year of Cooperatives, referenced in the kickoff planning as ambient context.

The line to say once: "That [the speaker-series Part 2 phrase] is your committee's language, not mine. ICN is one attempt to be that backbone."

Boundary: Say it once. Don't sermonize. Don't repeat. The phrase "materially exist, not just ideologically exist" lands once. Pause. Wait.

§6 — What the ecosystem needs to remember (deck slide 6)

On screen:

• 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.

Each record, defined and explained:

Member standing

• Plain meaning: who is currently a full member of the co-op, who is provisional, who has departed, when each transition happened, under what governance authority.
• How it breaks today: spreadsheets, mailing lists, the founder's memory. When a founder leaves, half the standing knowledge leaves with them.
• What ICN does about it: signed records of member admission, transition, and exit, verifiable by anyone with the receipt, independent of any platform. Not membership management (that's the co-op's job). Membership evidence (so a new treasurer can answer "who actually voted on this in 2027?" in 2030).

Decisions and approvals

• Plain meaning: what the co-op decided, when, by whom, under what authority (board vote, member referendum, working-group consensus), with what threshold met.
• How it breaks today: meeting minutes in Google Docs, decisions in Loomio, approvals in email, follow-through in someone's head.
• What ICN does about it: decisions become signed records linked to the proposal that triggered them, the threshold that was met, and the effect they authorized. Verifiable to a future board, a funder, a regulator.

Governance documents

• Plain meaning: bylaws, operating agreements, policies, board resolutions, anything that constitutes the co-op's rules.
• How it breaks today: governance documents drift between PDF versions; the "current" bylaws are whoever last edited the master doc.
• What ICN does about it: governance documents are versioned and signed; an adoption is a receipt linked to the decision that adopted it. The "current bylaws" question has a verifiable answer.

Advisor and service-provider handoffs

• Plain meaning: when a lawyer is engaged, what scope; when a CPA is retained, what authority; when a co-op developer transitions out, what knowledge transfers.
• How it breaks today: engagement letters in email, scope in advisor memory, handoffs at the moment someone goes inactive.
• What ICN does about it: an advisor relationship can be represented as an obligation across an organizational boundary, with scope and evidence of work delivered. Not legal practice management (that's the advisor's tool). Provenance of cross-boundary commitments.

Patronage and capital-account history

• Plain meaning: the records co-ops keep for each member's economic participation — labor contributions, internal capital account balance, patronage refund allocation, equity buy-in or buy-out.
• How it breaks today: spreadsheets, accounting exports from QuickBooks, advisor memory, the CPA's working papers. Opaque to members. Hard to verify across founder rotation or platform migration.
• What ICN does about it: these records can be represented as settlement, obligation, allocation, position, and receipt — the regulatory-safe vocabulary. The boundary between governance evidence (the decision to allocate) and accounting record (the books-of-record entry) is intentional. ICN holds the first. The CPA holds the second. Both verify each other.

Inter-cooperative trade, obligations, and federation evidence

• Plain meaning: what one co-op owes another, what was traded, what federation a co-op belongs to, what joint commitments exist.
• How it breaks today: bilateral contracts, email threads, federation membership records in someone's head.
• What ICN does about it: federation primitives that let co-ops verify each other's claims, settle obligations across boundaries, and surface trust over time. Not a marketplace. Not a clearing house. Verifiable evidence of relationships.

Records future members, boards, CPAs, counsel, or partner co-ops may need

• Plain meaning: the catch-all — anything that has to be available later to someone who wasn't there.
• What ICN does about it: content-addressed, signed, durable records that don't require trusting a vendor to verify.

The pattern this slide is naming: each of these records belongs to the cooperative now, but might need to be verifiable to a partner co-op, federation, or future member later. The difference between an ecosystem that materially exists and one that's only shared values is whether the verification works without a common platform.

§7 — ICN in one breath (deck slide 7)

On screen, seven words: Standing. Authority. Decision. Obligation. Receipt. Evidence. Review.

Each word, defined briefly with a co-op example:

The why-this-matters sentence (in Matt's voice): "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."

Boundary: ICN is the substrate. It doesn't know what a worker co-op is or what a Summit is. Apps that sit on top of ICN add the domain meaning. The seven words are kernel-level primitives that apply to any democratic organization.

§8 — What ICN is not (deck slide 8)

On screen:

• 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.

Each non-claim, explained briefly:

Not replacing Launch

The work of forming co-ops — the wizard, the document portal, the advisor surface, the multilingual UX — is Launch's territory. ICN does not do that work. If Launch's graduates eventually need durable post-formation records, ICN may be a layer they hand off into. That's a seam, not a replacement.

Not replacing TA providers, lawyers, CPAs, or co-op developers

The human work of cooperative formation, governance, conflict resolution, legal opinion, and accounting is irreducibly human. ICN does not automate any of that. ICN holds the evidence of work that humans did.

Not accounting software

ICN does not produce general-purpose financial statements, tax filings, or books of record. A CPA running QuickBooks remains the system of record for the co-op's accounting. ICN holds the governance evidence and provenance that runs alongside accounting (the decision to allocate, not the book entry itself).

Not financial-intermediary software

ICN is not a bank, payment app, wallet, token, currency, money transmitter, or speculative crypto product. The longer non-claim list (no wallet / no token / no payment rail / no crypto frame) lives in the speaker-note expansion if she asks directly. ICN uses cryptographic verification as record integrity, not as a casino.

Not production-ready or a pilot ask

ICN is pre-pilot. The substrate (daemon, gateway, identity, gossip, ledger, governance primitives) runs and has been deployed on a small cluster since December 2025. The human-facing surfaces (member-facing wallet UI, steward dashboard, production federation) are not live. This is a discovery conversation, not a partnership ask, not a launch announcement.

Boundary: This slide is on screen briefly. The list is here to show I know what ICN is not claiming. Don't dwell. If she asks, expand. Otherwise, move past it.

§9 — A useful test, if anything here feels real (deck slide 9)

On screen:

• 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.

What a "tabletop" actually looks like in practice:

1. Choose a workflow. Could be fictional ("a five-member worker cooperative forms in Albany in 2027, runs for three years, has its first capital-account allocation") or sanitized from a real past project ("a real co-op McKenzie worked with, names and numbers stripped").
2. Walk it beat by beat. Founding team identified. Charter drafted. Bylaws adopted. Members admitted. First fiscal year closes. First patronage cycle. A founder departs. A second co-op approaches about joint purchasing.
3. At each beat, ask three questions:
   • What record is generated?
   • Who needs to verify it later (member, board, CPA, counsel, partner co-op, regulator)?
   • What should not be a record (private deliberation, care work, conflict that resolved interpersonally)?
4. Capture what works and what breaks. If ICN's substrate can carry the work cleanly, that's a real seam. If it can't, that's also useful — it tells us what's missing or what should stay outside.

What this is not:

• Not a pilot. No live data. No partnership commitment.
• Not a sales demo. Not a product evaluation.
• Not Launch validating ICN. Launch is doing its own work; this is a parallel conversation.

What it could lead to: A second conversation where someone with co-op-lawyer or CPA expertise joins. Or a clear "this is not the right time" with reasons.

§10 — The question for today (deck slide 10)

On screen, the closing question:

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

Why this is the closing: It hands the call to McKenzie. The whole meeting comes down to whether the next conversation happens. Three possible useful answers: (a) "here's where the map is right" — names the seam; (b) "here's where the map is wrong" — names a gap or misframing; (c) "I need to think" — names a follow-up date.

Boundary: After reading the question, stop talking. Don't fill the silence. Don't soften the ask. Don't add "or whatever, no pressure."

§11 — FAQ: questions she might ask

Likely questions in roughly the order they might come up.

"How is this different from Loomio?"

Loomio records that a vote happened. ICN's receipts let someone who wasn't there verify that the vote happened, what was decided, under what authority, with what threshold. Loomio's records live on Loomio's servers; ICN's records live on hardware the co-op controls and are verifiable independently of any vendor.

"How is this different from QuickBooks?"

QuickBooks is the system of record for the co-op's accounting. ICN does not replicate that. ICN holds the governance side of economic events: the decision to allocate, the authority that approved it, the obligation it created. Both verify each other. The CPA still does the books.

"How is this different from a Drive folder of governance docs?"

A Drive folder is fine until you need to verify that a specific version of bylaws was adopted on a specific date by a specific quorum. Or until Drive changes its terms or the founder who owned the folder leaves. ICN's records are signed, content-addressed, and verifiable across years and platform changes.

"Is this a blockchain?"

No. ICN is peer-to-peer infrastructure. Each cooperative runs its own node. The cryptographic verification is for record integrity — proving that a decision happened and was authorized — not for tokens, currency, transactions, or speculation. If anyone reads "decentralized" and thinks Web3, they're reading the wrong project.

"How much does it cost?"

Pre-pilot. There's no pricing model because there's no product to price yet. Long-term intent: ICN is infrastructure that cooperatives own, run, and govern. Not SaaS rent.

"Who's funding it?"

Pre-pilot work has been self-funded and volunteer time. The roadmap includes grant applications (Mozilla, NLnet, Sovereign Tech Fund). The longer answer lives in the grant narrative core in the repo.

"What's actually built?"

• The substrate runs: daemon, gateway, identity, ledger, governance primitives, gossip protocol, federation primitives.
• A K3s cluster has been deployed and running since December 2025.
• ~272K lines of Rust, ~2,287 tests, ~75% to first external deployment.
• The human-facing surfaces (member wallet UI, steward dashboard, production federation) are not live. Those are next.

"Who else is using it?"

Pre-pilot. NYCN/Summit is the intended first reference institution. Launch is a discovery conversation, not a pilot. The "we" is a small group, not a deployed network.

"Why won't this just become another vendor we're locked into?"

The substrate is open source. Each co-op runs its own node. Federation is opt-in. Records are content-addressed and verifiable without ICN being in the loop. The lock-in case requires us to become a vendor, which is the opposite of the design.

"What if my co-op doesn't want all this technical infrastructure?"

Then your co-op doesn't use it. ICN is for the seam where Launch ends and durable governance begins, if that seam is real for a given co-op. Many co-ops will never need this layer. That's fine.

"What's the relationship to NYCN?"

NYCN is the intended first reference institution — a real cooperative ecosystem whose recurring work lets ICN test whether its primitives can support actual democratic institutional life. Not a customer. Not a demo. A worked example.

"Is ICN trying to be the Summit?"

No. The Summit is an annual gathering. ICN is the infrastructure that lets the ecosystem between Summits actually coordinate — site visits, year-round collaboration, statewide chapter, between-event continuity. The Summit's content (ecosystem mapping, cross-sector parity, statewide bridging) names what the field is reaching for. ICN is one attempt at the substrate.

"What's the threat model?"

The threat model lives in docs/security/threat-model.md. Short version: ICN assumes adversarial behavior by default (Byzantine actors, replay attacks, network adversaries, malicious peers), uses cryptographic signatures for authenticity, uses content addressing for integrity, uses peer-to-peer transport with TLS for transport security, and isolates kernel from app domains so a compromised app cannot subvert protocol invariants.

"What about privacy?"

Default privacy posture: nothing is public unless explicitly published. Member-private records stay on member-controlled hardware. Cross-coop verification works with hashes and signed claims, not raw data exposure. The privacy model has explicit primitives in icn-privacy.

"Who can I talk to about this besides you?"

Pre-pilot, the project is small. The right next step if a seam is real is to bring in a co-op lawyer, a CPA familiar with patronage allocation, or a TA provider who has lived through the records-survival problem. Not to demo more ICN.

"Have you talked to USFWC about this?"

Some conversations with people in that orbit (Worker Place, Cooperation Buffalo, ICA Group, DAWI). No formal USFWC engagement. If the seam is real, that's a natural next conversation.

"What's the long-term goal?"

For the cooperative and solidarity economy to materially exist as a coordinated ecosystem — governance, obligations, federation, evidence — on infrastructure the movement owns and runs, rather than infrastructure rented from vendors whose business models contradict ours.

§12 — Glossary

Terms ICN uses, with plain meanings and (where relevant) the regulatory-safe vocabulary that replaces forbidden financial language.

§13 — Boundary reminders (quick reference)

Quiet, not defensive. Say only if she misreads or asks directly.

• Still pre-pilot. Not production-ready, not externally audited, not legally or regulatorily certified.
• Not replacing Launch, TA providers, lawyers, CPAs, bookkeepers, or co-op developers.
• Not accounting, payment, banking, or wallet software.
• Not a token, currency, blockchain, or speculative crypto project.
• Not a formally committed Launch pilot. Not a formally committed NYCN pilot.
• No real Launch, NYCN, or private partner data in git for this work.
• Receipts alone do not prove legitimacy. Authority shortcuts must label themselves.
• Vocabulary: settlement, obligation, allocation, unit, position, receipt, provenance, evidence. Avoid the forbidden financial / crypto vocabulary listed in the Thursday brief.

One recurring point, said once during the call, never as a sermon: the cooperative and solidarity-economy ecosystem should materially exist, not just ideologically exist. Cite the 2025 Summit material (ecosystem-mapping session, upstate-downstate vision, cross-sector parity, EOC, the speaker-series Part 2 phrase) — that's your committee's language, not ICN's vocabulary.

Related reading

• Thursday meeting brief — controls facts and non-claims.
• Prep packet — private command center.
• Screen deck (browser version, PowerPoint) — what's on screen during the call.