Launch + ICN / Meeting Prep, 2026-05-21

This packet is Matt's private prep for a reciprocal conversation with McKenzie Jones. The goal is to learn Launch's workflow and ecosystem better, share enough ICN shape to make a possible continuity seam visible, and ask where the map is wrong.

The Thursday brief (`ICN_THURSDAY_MEETING_BRIEF_2026-05-21.md`) controls meeting-safe project-state facts. This packet controls conversational shape. If they disagree, the brief wins on facts.

0. Relationship context

This is not a cold meeting.

McKenzie Jones, founder of The Worker Place, President and Co-Founder of Launch Cooperative, building Launch with comp.coop.
Known collaborator from the 2025 NY Co-op Summit content committee. Ran the "Platform coops / tech tools for coops" session. Direct context on tech-for-coops failure modes.
Prior email contact and scheduled 1:1 context. Not a cold pitch.

She initiated the meeting as reciprocal: she wanted to learn more about ICN and share more about Launch.

The live doorway she opened was concrete: decision-making, member standing, patronage, and internal capital-account records. Use those nouns first. Do not lead with "internal economic memory." That is ICN translation language, not the first phrase out of Matt's mouth.

Top live note: "Who else is in the room?" Her May 1 email mentioned "another member who is curious." Identify them before launching into substance.

1. Correct posture: learner-first, Launch-first

The posture is:

I want to understand Launch's workflow and ecosystem better. I'll share enough ICN shape to ask better questions. Tell me where this map is wrong.

This is a reciprocal conversation, not a product demo, repo tour, or ICN manifesto. McKenzie has direct co-op development practice through The Worker Place and is building Launch with comp.coop. Assume domain expertise. Do not teach her field back to her.

Do not run the show. Show enough ICN shape to make the question intelligible, then get back to Launch's map.

If a sentence Matt is about to say sounds like a pitch, a feature claim, or a finished-product line, stop and rephrase as a question.

One recurring point to drive home, quietly, at least once: ICN's reason for existing is to let the cooperative and solidarity-economy ecosystem materially exist instead of only ideologically existing. Hit it once verbally. Do not sermonize it. The full framing lives in §4 below.

2. Public research on Launch, comp.coop, and The Worker Place

Read before the call so the cheat-sheet phrasing carries her vocabulary, not ICN's.

Launch.coop

Public framing: an online platform helping people create, grow, and sustain worker cooperatives in the U.S. (Not merely formation intake.)

Accessible steps and onboarding questions that act like a decision tree.
Prompts the right service-provider conversation at the right time (lawyers, CPAs, co-op networks, other TA).
Features: teams, tasks, comments, hiring service providers, secure document portal, advisor / co-op-developer workflow support.
Accessibility: easy-to-read language, graphics/multimedia, mobile-optimized, print options, English + Spanish with room to expand.
Two user groups: co-op founders, and advisors / service providers.
Co-op founder needs: vision, business plan, financial projections, governance documents, service providers, financing opportunities, broader co-op movement context, educational resources.
Advisor needs: access materials, organize client work, track documents, share with clients, track changes, project maps, client connection.
Diagnosed problems: no single federal co-op policy, state variation, TA bottlenecks, scattered/static PDFs, language and access barriers, low online visibility of co-ops.
Does not replace TA. Reduces repeated intro questions; helps TA providers manage co-op clients.
Spanish-language page lists pricing tiers (Startup, Solidarity Discount, Full Cost, Redistribution Rate, Advisor Account). Treat as public-but-possibly-staging. Do not foreground pricing.

comp.coop

Worker-owned tech collective: engineers, designers, consultants.
Brings high-end tech to worker-led businesses without the VC model.
Can act like CTO capacity for worker-led businesses.
Use this to ask about technical boundary and stewardship, not to speculate.

The Worker Place

McKenzie's co-op development practice.
Services: governance documents, decision-making processes, fundraising and loan readiness, membership onboarding, networking and partnerships, conflict resolution, grievances, accountability, member turnover, management, operations, bylaw change.
Implication: McKenzie is not just a "platform contact." Her vocabulary leads.

3. First five minutes: learn their map

Before introducing any ICN structure, run this:

"Who else is in the room?" (Identify the second curious member.)
"I'd love to start with Launch. Where does Launch think formation begins and ends? Where does it sit in the lifecycle of a co-op?"
"What does the workflow actually look like inside Launch? What are the main states a group moves through?"
"What are the first three things co-ops come back to you about after formation?"

Listen. Take notes. Do not translate yet. The first five minutes are for capturing her vocabulary so the rest of the meeting can borrow it.

4. The seam to explore (one sentence)

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.

That is the anchor. Everything else is there to test whether the anchor holds.

The ecosystem stake (the recurring point to drive home)

This is not invented framing. It is the 2025 Summit's own stated purpose, written by the organizing committee Matt sat on. Concrete citations:

Ecosystem mapping was one of the top-rated sessions of the 2025 Summit (per the Lessons Learned doc): "the variety and quality of the sessions and speakers, with specific mention of the keynote, ecosystems, policy, financing, and conflict management sessions."
McKenzie's stated vision at the 12/4/2024 kickoff: "upstate / downstate connections, bridge the movement for state action," "build cooperative power across the state," "role of philanthropy in supporting cooperatives," "Equity Agenda work on creating an employee ownership center in NYS."
The Lessons Learned doc names as recurring asks: cross-sector parity (worker, consumer, financial, ag, housing), regional events between annual summits, a statewide directory of co-ops, a shared marketing identity / statewide brand, and an NY state employee ownership center.
The 2025 Summit speaker-announcement series, which Matt's marketing committee published, teased Part 2 as: "the infrastructure builders designing the legal, technological, and organizational backbone that lets co-ops scale." That is the layer ICN is trying to be.
2025 was the UN International Year of Cooperatives, which was referenced in the kickoff planning as ambient context for why this year mattered.

The cooperative and solidarity economy already exists ideologically: charters, principles, 180 years of practice, the Rochdale principles, the ICA, the Mondragon corpus. What it does not yet have is the shared infrastructure to materially exist as a coordinated economic and governmental ecosystem between annual gatherings, across organizations, across years, across upstate–downstate distance, across cooperative sectors. That is what the 2025 Summit kept reaching for, in different vocabulary, in every session.

ICN is one attempt to be that substrate. Governance after formation, durable membership and standing, inter-cooperative obligations, patronage and capital-account history that survives founder rotation, federation that does not require surrendering autonomy to a common platform. A nervous system for an ecosystem, in the language of the planning docs, not a wallet or a payment app.

Hit this point at least once during the conversation. Cite the 2025 Summit's own framing, not ICN's vocabulary. Then return to listening.

The live priority from the email thread

Patronage and capital-account history. These records can drift into spreadsheets, accounting exports, advisor memory, or systems members cannot easily interpret later. The question is not whether ICN should own that work. The question is where governance evidence meets accounting record, what must remain outside ICN entirely, and what shape the ecosystem-level layer should take.

5. Quiet non-claims

Present, not repeated. Don't lead with these. 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 is 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.

6. Launch-specific questions

Run after the first-five-minutes block. Pick what fits the room. Leave silence after each.

On Launch's workflow

Where does Launch think formation begins and ends?
What are the main states a group moves through inside Launch?
How do teams, co-founders, advisors, documents, tasks, comments, and milestones work together inside Launch?
Which records matter only during formation, and which matter later?
When do governance documents become "official" in Launch's view?
Where do decision-making and member standing show up in the workflow today?
What do advisors actually need to see, and what should they be able to attest to?
What should Launch never touch?

On patronage and capital-account history (she opened this)

"Tell me which co-op projects you wished you had this for. What broke, or what couldn't you do?"
Where do patronage, capital accounts, allocations, financial projections, or accounting handoffs show up in the workflow today?
Who actually needs to trust those records later: members, fiscal sponsor, buyer of a member's interest, future board, attorney?
What is governance evidence vs. accounting record vs. professional execution (CPA territory)?
Where does it break today: founder rotation, advisor turnover, fiscal-year close, member exit, dissolution?
What should ICN never touch here?
Is there a sanitized co-op case she has in mind, with names and numbers stripped, that we could rehearse against?

On the ecosystem

What is comp.coop's role in this picture, technically and as a steward?
What would make Launch more powerful five years from now?
Who else is doing the post-formation work she is describing?
Where does Launch overlap or conflict with TA providers and co-op-developer networks she works with?

On boundaries

What must stay human and process-first?
What should expire?
What should never be public?
Where would a receipt help, and where would it become bureaucracy?

7. A 60-second opener (optional, only if she asks for the ICN shape)

Read in Matt's voice. Direct, dry, conversational. Use only if she explicitly invites the ICN side.

Launch is trying to make starting a worker co-op less like wandering through a legal, financial, and governance junk drawer with a flashlight dying in your mouth. You break it into steps people can move through: teams, documents, tasks, advisors, service providers, milestones.

ICN is asking the next-layer question. Once those steps become real institutional facts, how does the co-op remember them. Who has standing. Who was authorized. What decision happened. What obligation followed. What evidence survives when the advisor, organizer, or founding team rotates out.

I want to understand whether there is a clean seam between Launch's workflow and the layer ICN is working on, or whether that seam doesn't exist yet.

If she doesn't ask, skip it. The opener is a tool, not a script.

8. Translation table

Use only when she reaches for the abstract layer. Her word goes first.

Launch surface	ICN substrate question
Founding team / co-founders	Who has standing?
Roles / advisor relationship	Who can act, review, guide, or certify?
Formation path selected	What process is this group actually in?
Governance doc drafted	Under whose authority does this artifact sit?
Task assigned	Who owes what by when?
Service provider engaged	What obligation exists across the boundary?
Milestone completed	What effect happened?
Approval / confirmation	What receipt exists?
Document / change history	What evidence survives?
Launch handoff into operating co-op	What standing / authority carries forward?
Patronage and capital-account history	What is governance evidence vs. accounting record?

9. Walkthrough beats (only if she wants to walk one)

Walk one beat at a time. After each, ask: how does this happen today? what state needs to persist? who needs to trust it later? where would a receipt help, and where would it become bureaucracy?

Group enters Launch onboarding.
Founding team / co-founders identified.
Roles and advisor / TA / provider relationships established.
Formation path selected.
Governance documents drafted.
Tasks assigned to co-founders, advisors, providers.
Legal / accounting / co-op-developer service-provider loop triggered.
Decision or milestone completed.
Member standing / board authority / operating roles established.
Patronage and capital-account history becomes relevant.
Handoff into ongoing governance.

The walkthrough's purpose is to find the beat where the room says "that is where it breaks today."

10. Layering (private clarity; do not lecture in the room)

ICN is the substrate: generic primitives (standing, authority, obligation, receipts, evidence) and the constraint engine that enforces them. Institution packages are a reusable meaning layer on top: role maps, workflow templates, fixtures, rehearsal scripts. NYCN/Summit is one such package being built first, against a real cooperative ecosystem, to stress-test the primitives.

A worker-cooperative-formation package is one possible future shape this conversation could surface. Don't pitch the layering. It is background.

Full clarification (private reading): `ICN_NYCN_INSTITUTION_PACKAGE_BOUNDARY.md`.

11. Backup shared context (only if useful)

If the formation seam is too abstract, a sanitized example from the recurring-event domain is available: session becomes public program; speaker, vendor, accessibility, sponsor obligations; cross-year handoff. Use as a shared reference pattern between two people who have run that work together, not as an ICN topic. The Summit reference work lives at `NYCN_SUMMIT_REFERENCE_INSTITUTION_STRATEGY.md`.

12. What "good" looks like

A short list of post-formation problems co-ops actually bring back to Launch.
McKenzie's own words for those problems (write them down verbatim).
A read on whether the patronage and capital-account history seam feels real from Launch's side.
A read on whether "InterCooperative Network" lands clearly or triggers the wrong association.
An agreement or non-agreement about whether a follow-up makes sense.
One sanitized walkthrough candidate, if useful.

13. Post-meeting capture

Fill within 24 hours. Sanitized only.

Launch's vocabulary for post-formation problems (verbatim):
Patronage / capital-account / accounting questions surfaced:
What Launch validated:
What Launch rejected or said was overbuilt:
Clean seam identified:
Seam rejected or not ready:
Smallest rehearsal candidate:
Who else should join (lawyer, CPA, TA provider, federation organizer):
Follow-up action / cadence:
Docs / artifacts to revise:
No-go zones: