The Boundary Campaign — Complete Packet
Jerry Michalski · drafted July 7, 2026 · weekly arc starting mid-July
The spine: "Your organization is deciding right now, mostly by accident, how much of its thinking to outsource. I've spent thirty years on the other side of that line, and I can show you what it looks like from there."
The tone throughout: grace toward aware leaders. These are forces they likely haven't decided how to shape — never negligence. The audience is the leaners-in: corporate explorers actively and positively working the boundary between human and machine intelligence.
The structure: show-then-name. Dispatches show something vivid; idea episodes give the concept to hold it with. Every episode ends by tossing a question back across the line, and trails the next episode.
The Seven-Week Schedule
| Week | Main beat (Tue) | Mid-week post (Thu) |
|---|---|---|
| 0 | Text post — the keeper line + grace note (final draft already approved) | — |
| 1 | V1 — The Scenarios (outline approved) | The Disappearing Question |
| 2 | V2 — Brain Tour dispatch | The Provenance Vacuum |
| 3 | V3 — Extended Mind / good Cyborg (outline approved, ask removed) | The Cyborg Ask |
| 4 | V4 — GFC Provenance dispatch | Cyborg Report-Back (or Prompt-Shaped Problem if comments run thin) |
| 5 | V5 — Snip! & Curation-as-Decision | The Many Names for the Global Brain |
| 6 | V6 — Design from Trust + the Invitation | The Unauditable Decision (as coda, keeping the theme warm while conversations develop) |
Bench material (Prompt-Shaped Problem, Unauditable Decision if unused) extends the rhythm into weeks 7–8 while inquiries mature. More material than slots is the right problem to have.
Mid-Week Post Drafts
1. The Disappearing Question (week 1)
There's a question your organization stopped asking recently, and nobody heard it go silent.
It's the question someone used to walk down the hall with. The quick ping to the colleague who'd know. Now an answer arrives in three seconds — smooth, confident, unsigned — and the walk never happens.
Each unasked question looks like efficiency. But questions were never just retrieval. They were threads: who knows what, who cares about what, who's worth asking twice. Ask enough of them and you've woven the informal map every organization actually runs on. Stop asking, and that fabric thins — quietly, and from the inside.
Nobody chose this. It arrived disguised as convenience, which is exactly why it deserves a deliberate look.
Where in your organization has a question gone quiet? And what did that question used to connect?
2. The Provenance Vacuum (week 2)
Somewhere in your organization right now, a number is about to make a decision — and nobody knows where the number came from.
It appeared in a summary. The summary drew on a draft. The draft drew on... something. When someone finally asks "where did this come from?", the honest answer is: we're not sure. Nothing in the chain has a signature.
This isn't fraud, and it isn't carelessness. It's what happens when generated text flows into decisions faster than provenance can keep up — a vacuum that forms one convenient step at a time, invisible until the moment you need to walk a conclusion back to its source and discover there's no path.
Here's a small audit worth an hour: pick one load-bearing conclusion your team acted on this month. Try to trace it to its origins. What you find — or can't — will tell you a great deal.
What did you find?
3. The Cyborg Ask (week 3, final draft already approved)
Last week I used a word that makes some people flinch, and I did it on purpose.
Cyborg.
Not the movie kind. The philosophers' kind: anyone whose thinking runs partly on chosen machinery outside their skull. By that definition you became one long ago — the notebook, the whiteboard, the spreadsheet, and now the model. The question was never whether you'd be a cyborg. It's whether you'll be a good one.
And by good I emphatically do not mean obedient. I mean effective. The bad cyborg is shaped by its tools: it accepts the summary, ships the first draft, frames every problem as a prompt. The good Cyborg shapes the pairing — delegates deliberately, keeps a hand on the tiller, and gets more capable, more itself, with every extension it chooses.
But I hold this word loosely, and I'd like your help steering it. Does "good Cyborg" land for you — or does the flinch cost more than the spice is worth? Is there better language for a person whose tools amplify their judgment rather than replace it?
I'm serious about this: whatever we find together, I'll use. That's rather the point.
4. The Prompt-Shaped Problem (bench / week 4 alternate)
Watch what happens to questions inside an organization that thinks in prompts.
Slowly, without anyone announcing it, problems start getting framed in the shapes the tool can answer. The messy question becomes the tractable one. The strategic ambiguity becomes a request for a list. The instrument doesn't just answer your questions — it starts quietly editing which questions occur to you at all.
The sharpest people I know use these tools constantly, so this is not a warning against the tools. It's a warning about an aperture: every instrument narrows the field of view in exchange for magnification, and that trade is only dangerous when nobody notices it's being made.
Here's the test: what's a question your team cared about two years ago that nobody frames anymore — not because it was answered, but because it doesn't fit the tools?
5. The Many Names for the Global Brain (week 5)
For over a century, thinkers from wildly different traditions have been reaching for the same idea — and each one gave it a different name.
Teilhard de Chardin called it the Noosphere. H.G. Wells wrote of a World Brain. The cyberneticists, the hypertext pioneers, the sensemaking researchers — Global Brain, collective intelligence, collective sensemaking, and more. I keep a running collection of these names in my Brain (of course I do), and the collection itself makes an argument no single name can: when theology, literature, systems science, and computing all independently sketch the same shape, something real is sitting there, waiting to be built.
We now have machinery those thinkers could only dream of. The question is whether we'll use it to become that — a genuinely smarter we — or merely to automate the me.
More on this in next week's video. Meanwhile: which of these names have you encountered? And which one carries the idea best?
6. The Unauditable Decision (week 6 coda)
Sometime next year, something in your organization will go wrong — that part is ordinary. Here's the new part: no one will be able to reconstruct why.
The reasoning that led to the decision won't be in anyone's head, or in any memo. It lived in a context window that's gone, a chat that wasn't saved, a summary of a summary. The decision will have consequences; the consequences will have no traceable author. That severing — outcomes cut off from the reasoning and the people who produced them — is an old pattern wearing new clothes, and it now happens at machine speed.
The organizations that will handle this era best aren't the ones that avoid the tools. They're the ones that keep their reasoning signed — where any conclusion that matters can be walked back to the judgment calls that made it.
What would it take for your most important decision this quarter to be auditable a year from now?
Video 2 — The Brain Tour (Frame)
Dispatch. Tour path is Jerry's to choose; this is the structure it drops into. Target 5–7 min.
1. Cold open — the callback. "Last week I named four ways thinking quietly changes hands inside organizations. This week I want to show you the alternative — not described, but taken to its logical extreme. You're about to see what thirty years of not outsourcing your thinking looks like."
2. The rules of the tour. "This is my Brain — 625,000 ideas, 1.2 million links, one per day-ish since 1997. Two rules before we go in. First: everything you're about to see is a decision I made — every link, a choice, and I can stand behind each one. Second: the hardest part of this tour, for me, is resisting the side doors. There are 625,000 of them. I'll show you three neighborhoods and keep my hands on the wheel."
3. Neighborhood one — [Jerry's choice: something playful/human]. Guidance: open with warmth, not gravitas — show the Brain is lived-in, funny, personal. Establishes terrain-not-trophy.
4. Neighborhood two — [Jerry's choice: something corporate-relevant]. Guidance: a thread a business viewer recognizes — a company, a market, a technology they know — showing how context accumulates around it across decades.
5. Neighborhood three — the surprising link. Strong candidate: the virtuous circles ↔ vicious cycles link — two ideas everyone knows separately, revealed as the same machine spinning in opposite directions. Show it here; V3 names what happened ("the judgment was built by building it") next week — show-then-name across episodes.
6. What this is not. "This isn't a filing cabinet, and it isn't nostalgia. I use AI every day — happily. This is about what I bring to that table: a mind I extended on purpose, one decision at a time, for thirty years."
7. The hanging question + trailer. "Now, the question a few of you are already forming: why would anyone do this? That question has a genuinely good answer, and it comes from philosophy, not productivity. Next week I'll give it to you — and I'll explain why, by the end of it, you may discover you're a cyborg. See you then."
Video 4 — The GFC Flyover (Outline)
Dispatch. The provenance demonstration. Target 5–7 min.
1. Cold open — the contrast, promised. "Ask a chatbot what caused the 2008 financial crisis. You'll get a smooth, confident, entirely reasonable summary. Today I want to show you what that summary leaves out — and why the omission matters for every decision your organization makes on generated text."
2. Callback. "Two weeks ago I argued that an extension of your mind should be one you chose and can audit — one that's signed. Here's what signed knowledge actually looks like, on the hardest kind of question: why did something enormous happen?"
3. The flyover — one thread, ninety seconds, no side doors. The path: the bipartisan homeownership push (demand-side politics) → the deregulation cluster — Gramm-Leach-Bliley, the CFMA, the SEC net-capital change (supply-side fuel) → private-label securitization as the engine → NINJA loans as the artifact everyone remembers → consequences landing on people who never made the decisions. Delivery note: each node gets its date and its decision-makers named. The discipline is the demo — resist every branch.
4. The contrast, delivered. "Now ask the model the same question. What comes back is pre-averaged: no scars, no signatures, no account of who decided what, when, and who paid for it. It's not wrong, exactly. It's unaccountable — a conclusion with the reasoning amputated. And you can't interrogate an average."
5. The corporate turn. "Your organization increasingly runs on summaries like that one. So here's the question worth an uncomfortable minute: of the load-bearing conclusions your team acted on this quarter, how many could you walk back to their sources — to the actual decisions, signed by actual people?"
6. Trailer. "There's a name for the pattern you just watched — decisions severed from their consequences. I've been collecting examples for years, and 2008 is only the most famous episode. Next week I'll give you the name, and show you the severing happening again right now, in a new place. See you then."
Video 5 — Snip! and the Curated Mind (Outline)
Naming episode for V4. Target 5–7 min.
1. Cold open — the name. "Last week you watched decisions get severed from their consequences — people who chose, insulated from what the choosing caused. I call that pattern Snip!, and once you have the name, you'll see it everywhere."
2. The pattern, generalized. "2008 was one episode. But Snip! is a family: finance, war, governance, the attention economy — every domain where the hand on the scissors never feels the cut. And the newest member of the family is the one running through everything in this series: conclusions severed from the reasoning that produced them. Every unsigned summary is a small Snip."
3. The antidote — curation as decision. "The opposite of the severing is the signature. A friend of mine, Jochen, put it in six words I've never improved on: every link is a curatorial decision. Knowledge someone chose, connected, and stands behind — that's what you saw in the Brain tour, and it's what the smooth consensus can never give you, because averaging is the opposite of deciding."
4. The widening — memory as fabric. "Here's the deeper history. Before writing, memorized stories and songs were society's long-term memory — and reciting them together was the social fabric itself. Remembering was something we did as a we. Organizations, oddly, are among the last oral cultures on Earth: their real knowledge lives in conversation, apprenticeship, the question asked down the hall. Which is why the disappearing question and the unchecked summary aren't productivity issues. They're the fabric thinning."
5. The corporate turn. "So the question for your organization isn't 'how much AI?' It's: as the tools arrive, does your shared memory get more woven or more severed? Does anyone still sign the fabric?"
6. Trailer. "Next week, the final episode: the design stance I'd bring to that question — how to adopt these tools so your people compound instead of atrophy — and an invitation for those of you who want to explore this boundary together. See you then."
Video 6 — Design from Trust, and an Invitation (Outline)
Naming episode + the offer. Target 6–8 min.
1. Cold open — full circle. "Six weeks ago I said your organization is deciding right now, mostly by accident, how much of its thinking to outsource. Today: what deciding on purpose looks like."
2. The stance — Design from Trust. "Most AI adoption is Design from Mistrust: deploy the tools to check, police, replace, and squeeze. There's another stance — Design from Trust: deploy them to compound your people. Same tools, opposite question. Mistrust asks 'what can we stop paying humans to do?' Trust asks 'what could our humans do now that they couldn't before?' Every scenario from week one has a trust-shaped answer: summaries somebody signs, drafts that start with thinking, ladders rebuilt with new rungs, disagreement kept deliberately alive."
3. The destination — named at last. "And here's where this has been heading all along. One person pairing well with these tools — a good Cyborg, effective, not obedient — is a fine outcome. But a room of good Cyborgs, sharing memory that's provenanced and signed? That's something bigger: collective human intelligence — an organization genuinely smarter than any of its tools, or any of its people alone. Humanity has been circling this idea for a century under a dozen names. We're the first generation with the machinery to build it. Some of us are already trying — ask me about the Big Fungus sometime."
4. The invitation. "If you're the person in your organization thinking hardest about this boundary — and if you've watched this far, you probably are — here's what exploring it together looks like. You bring your actual tangle: the AI question your organization is living inside. In a focused working session, we map it — genuinely map it — and you leave with the map, a vector, and a quest. I won't promise transformation; anyone who does is selling something. I promise you'll see your situation more clearly, and you'll know your next three moves. I've spent thirty years on the other side of the line. Come look at your question from over here."
5. The hand. "There's a link below — a page that explains the working sessions and how to start a conversation with me. Or just comment, or write to me directly. I read everything."
6. Close — the line, inverted. "Your organization is deciding right now how much of its thinking to outsource. My whole message, after six weeks, is four words: decide it on purpose. Thanks for walking the boundary with me."
Production Checklist
Cadence & buffer. Record V1 and V2 in your first week home so you're always one video ahead; the buffer is what makes weekly sustainable. Videos publish Tuesdays, mid-week posts Thursdays (adjust to your audience's rhythm, but keep it consistent).
Division of labor. You: talking-head beats and Brain screen-recordings with live narration, raw takes kept. Jenn (Descript power user): post-production — cuts, captions, filler-word cleanup, thumbnail exports, YouTube upload and description. Consider a standing weekly handoff slot so post-production never queues behind travel.
Platform mechanics. YouTube is home base; every video lives there in full. On LinkedIn, never put the YouTube link in the post body (the algorithm buries external links) — instead post either a native 60–90 second excerpt with "full version on YouTube, link in comments," or a text post distilling the video's argument with the link in the first comment. The mid-week text posts need no links at all; they're pure fishing.
Titles & thumbnails. Question-led titles outperform statements for this material ("Is Your Org Outsourcing Its Thinking?" beats "On Cognitive Outsourcing"). Thumbnails: your face + the Brain's plex is a genuinely distinctive combination nobody else on the platform can produce — use it.
Comment tending. The comments are the point — they're where your first clients surface. Reply within 24 hours, personally, especially to anyone matching the corporate-explorer profile. Warm commenters get a DM, not a pitch: "loved your comment — curious what prompted it." Harvest their language; the words they use for their problem are the words the offer page should use.
Signals to watch weekly. Comments from target-profile people (titles like head of AI enablement, innovation lead, chief of staff); DMs and connection requests with notes; profile views trend; and above all any variant of "can we talk?" Two of those in six weeks is a working funnel.
Before V6 ships. The offer page (Framer) must be live — V6's beat 5 points at it. Build it in week 4 or 5 from harvested comment language. Pricing/framing decisions: see the live conversation.