Boundary Offer — Thirteen-Post Sequence
Spine one, elaborated. Resequenced Aug 8, 2026 to match what's actually published — the first four posts are locked in as posted; everything from post 5 on is still open to move.
The through-line
The whole series teaches one association: you are the guide to the boundary between human and machine thinking. Not a fixer who guarantees outcomes — an explorer-guide who's lived on the far side of a line that organizations are now crossing mostly by accident, and who can show them what it looks like from over there. Every episode demonstrates one facet of that, and the credential (thirty years, 645,000+ ideas, the world's largest published Brain) always arrives as proof-of-work rather than as the headline.
The keeper line anchors everything:
Your org 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 audience is the innovation executive who is already leaning into AI, positively and on purpose, and wants to explore this boundary with intention rather than fear. You're never scolding them for using AI — you're handing them the naming and the map for something they already sense.
The tone rule, in three words: invitation over admonition. Nobody in this series did anything wrong. Convenience adopted for good reasons is a frontier, not a scandal.
The arc at a glance
- Launch text post — On Handing Over Your Thinking. Posted.
- Video 1 — The four scenarios: Ways We Give Away Our Thinking. Posted.
- Video 2 — The Brain tour: On Sensemaking. Posted — video is the real narrated dispatch; text is a companion reference list.
- Mini post — If a Thing Doesn’t Transit Your Neurons. Posted, off-plan but now counted in-sequence — cognitive offloading vs. cognitive surrender.
- Mini post — The disappearing question. Are You Talking To Your Colleagues Less? Every unasked question is a thread not woven.
- Mini post — The prompt-shaped problem. How Much Are We Adapting to AI? The questions narrow to fit the instrument.
- Video 3 — Extended mind. The reframe: "what am I extending my mind with, and who's accountable for that substrate?"
- Video 4 — The good Cyborg. The answer to Video 3's question, on purpose: effective, not obedient.
- Mini post — The provenance vacuum. Nobody knows where the number came from.
- Mini post — The unauditable decision. When it goes sideways, will the reasoning still exist?
- Video 5 — The GFC provenance flyover. The demonstration: signed human memory vs. a smooth, unsigned summary.
- Video 6 — Snip! and curation as decision. Every link is a choice; curated is signed, generated is unsigned.
- Video 7 — Design from Trust, the horizon, and the invitation. How to adopt AI so it compounds your people; a room of good Cyborgs as collective human intelligence; then the working-session invitation, planted not pitched.
Two mini posts prime Extended Mind (7); two prime the GFC flyover (11). Extended Mind and the good Cyborg (7–8) stay adjacent — the second completes the first's open question. GFC → Snip! → Design from Trust (11–13) stay adjacent too — one chained demonstration where each trailing hook assumes the one before it.
7. Video 3 — Extended mind
The pivot episode. This is the reframe that dissolves the fear the audience is carrying — the half that opens the question, without yet answering it.
The idea. Their cognition already doesn't stop at their skull. It never did — notebook, calendar, the colleague down the hall, the Brain on the screen. So the AI question was never "will it replace my mind?" It's "what am I extending my mind with, and who's accountable for that substrate?" That reframing takes the whole conversation out of fear and into design.
Visual: you to camera. Maybe a simple visual of the extension chain — notebook → colleague → Brain → AI — nothing fancy.
Trailing hook: "So if your mind already runs on more than your skull — the real question isn't whether to extend it. It's how to stay in the driver's seat while you do. That's next week." (→ the good Cyborg.)
8. Video 4 — The good Cyborg
The payoff to Video 3's open question, now with room to stand on its own.
The idea. The thing people dread is becoming a Cyborg. But there's a good one and a bad one, and the difference is everything. A bad Cyborg is obedient — it does what the machine suggests, defers to the smooth answer, lets its own judgment atrophy. A good Cyborg is effective — it stays in the driver's seat and uses the machine to become more itself, not less. Effective, not obedient.
The community-naming move. End the toss-back by genuinely asking: does "good Cyborg" land for you? Is there a better word?
Visual: you to camera, possibly with a simple two-column contrast on screen — obedient vs. effective — nothing fancy.
Trailing hook: "Next week I'll show you what a good Cyborg's memory looks like when the stakes are real — a trillion-dollar mistake, mapped honestly." (→ the GFC flyover.)
Optional schwag tie-in, for later: the "Be a good Cyborg!" merch idea lives naturally off this episode if it catches.
9. Mini post — The provenance vacuum
A decision gets made on a number or a claim, and when someone finally asks "where did this come from?", the honest answer is: nobody knows. Nothing in the chain has a signature.
Close: could your organization reconstruct the source of the last big number it acted on?
10. Mini post — The unauditable decision
Something goes wrong, and no one can reconstruct the reasoning that led there — the chain of thought lived in a context window that's gone. Decisions severed from their consequences, at machine speed.
Close: when your last decision goes sideways, will the reasoning still exist to learn from?
11. Video 5 — The GFC provenance flyover
The demonstration episode. Everything before this argued; this one shows.
The promise: watch provenance work when it matters. Take a single thread through the Brain — the legislation that enabled NINJA loans, the loans themselves, the 2008 consequences — and show the chain of decisions intact, each link signed by a human who made it. A ninety-second flyover on one thread, not a tour of the whole crisis.
The contrast that lands it: put that beside what a chatbot gives you when you ask about the same crisis — a smooth, pre-averaged summary that reads plausibly and carries no signature at all. Same subject; one map is accountable and one is not. That difference is the entire value proposition, made visible in two minutes.
Visual: the GFC thread in the plex, then (optionally) a screen of generic AI summary text beside it for contrast.
Trailing hook: "That accountability isn't a feature of the software. It's a decision I made 625,000 times. Next week: why every one of those links is a decision — and what gets severed when the reasoning disappears." (→ Snip!.)
12. Video 6 — Snip! and curation as decision
The idea underneath the whole practice, named.
The promise: explain Snip! — what happens when conclusions get severed from the reasoning and the consequences that produced them. The unchecked summary, the smooth consensus, the sawn-off ladder from Video 1 were all instances of one thing: decisions cut loose from their provenance, at machine speed.
The turn: and here's the antidote you've been living. Every link in the Brain is a decision. The difference between curated knowledge and generated knowledge is the difference between signed and unsigned. The Brain's value was never the volume — it's that each of those 1.2 million links is a choice someone can stand behind. Curation is decision-making, made durable.
Visual: a link being drawn in the plex — the small, deliberate act — contrasted with a wall of auto-generated text.
Trailing hook: "So if that's the problem — and if signed memory is the antidote — the real question is how a whole organization adopts AI without severing itself from its own thinking. That's next week, and it's the one I care about most." (→ Design from Trust.)
13. Video 7 — Design from Trust, the horizon, and the invitation
The closer. The stance (Design from Trust), the horizon (a room of good Cyborgs as collective human intelligence, Big Fungus named lightly), and the door (the working-session invitation, planted not harvested).
The stance — Design from Trust. How do you adopt AI so it compounds your people rather than polices or replaces them? You design from trust rather than from suspicion. Most institutions armor themselves against their own members cheating, and end up too armored to think. Applied to AI, Design from Trust means building adoption that assumes and rewards good judgment — that makes people more capable, more themselves, more effective Cyborgs.
The horizon — collective human intelligence. Then lift the frame one level, gently. Picture a room full of good Cyborgs, each carrying provenanced, accountable memory, sharing it with each other. That's not a team using a tool. That's collective human intelligence — and it's the thing actually worth building. Name Big Fungus lightly here, as the invitation-to-come rather than a pitch: the idea that our thinking tools could find each other and leave the shared territory better than they found it.
The door — the working session. Now, and only now, the offer, planted not harvested: if any of this is live for you, there's a way to work on it directly. You bring your organization's actual AI tangle; we map it live in a focused session; you leave with the map, a vector, and your next three moves. No transformation promised — just a clearer frontier and a real next step. "If you're leaning into these questions on purpose, write to me. I read everything."
Visual: close on the plex, or on the boundary banner — one image that says the whole series in a glance.
Trailing hook: this one trails the session, not another video. The comment prompt invites the inquiry.
Settled logistics (reference)
Pricing (kept off the public page — inquiry by email or LinkedIn DM only): $3,500 single session; $8,500 half-day team session; $3,500/month retainer. The reply template for inbound inquiries is in the campaign packet.
LinkedIn banner text: Outsource your thinking on purpose. — pairs deliberately with the "mostly by accident" hinge in the keeper line.
Profile: rework the headline, banner, About, and Featured before the launch post goes up (full detail in the LinkedIn makeover file). Featured holds only the current story: pin the launch post, then Video 1, then the Framer page once it exists.
Framer offer page: added to Featured around week 5, once the first commenters have handed you their language to check the copy against.