Steal the Pattern, Don't Adopt the Head

When you study someone else's AI setup, steal the pattern: contracts, evals, draft gates, replaceable orchestration. Do not adopt their head as your brain. Your durable asset is memory and judgment you control. Their chatbot personality is disposable.

Builders love cloning stacks. Someone posts a dazzling agent harness and the timeline fills with "I'm switching everything to X." I have felt that pull. I have also paid for it.

The twin doctrine that keeps me sane is simple: the vault is the durable asset. The head is replaceable.

So when I read AIDB packaging, Every's essay craft, Levels' ship logs, or an exec's twin talk, I steal patterns. I do not move my source of truth into their substrate.

Pattern vs head

Pattern examples worth stealing:

• BLUF-first briefs
• Atomic share cards from a long essay
• Draft-not-send workflows
• Citation-required answering
• Eval gates before promotion to durable memory
• One pipeline with many triggers
• Weekly human timebox with agent assist around it

Head examples that should stay optional:

• A particular chat vendor as the only memory
• A mascot agent with a backstory
• A cloud routine that reimplements your job "lighter"
• A second brain app that cannot export cleanly
• Someone else's persona prompt pasted as your identity

Patterns transfer across tools. Heads want to own you.

How I steal without relocating my brain

1. Name the job. "I need packaging for builder notes," not "I need to become NLW."
2. Extract three mechanics. For AIDB-style media: thesis box, atomic shares, machine-readable index. Leave the daily news factory.
3. Map mechanics onto my vault. Files, frontmatter, evals I already trust.
4. Plug a head in temporarily. Cursor, Claude, Super Doer, Sage: workers against my contracts.
5. Prove replaceability. If the head vanished tomorrow, could I still find the notes and rerun the pipeline?

If step 5 fails, I did not steal a pattern. I rented a landlord.

Personal examples (public framing)

Builder Notes: Steal dual object (essay + short audio), share cards, skim anatomy. Keep drafts in my tree. Human publish click. No auto-post.

Morning brief: Steal the idea of a daily CoS artefact. Keep one codepath I own. Reject parallel cloud rewrites that drop sections.

Digital team: Steal department routing as capability bundles. Reject persistent multi-agent soap operas.

BJJ as training OS: Steal closed-loop practice (attempt, note, adjust). Do not import someone else's coaching cult as identity.

Photography / The Room: Steal assembly-line proof films. Keep consent and house style in my folders.

SMB to enterprise

SMB: Your Notion, Drive, or git repo is probably already the vault. Write AGENTS-style contracts at the root. Make tools come to the files. When a vendor shines, wrap it as a head with an export test.

Enterprise: Platforms will sell you a head: copilots bound to their graph. Fine as labour. Dangerous as system of record. Demand:

• Exportable memory
• Policy as code (not only as wiki)
• Eval evidence for high-risk actions
• Clear send and approval rights
• Ability to swap model vendors without rewriting the operating model

The pattern is an internal control plane. The head is a worker behind an API.

The emotional trap

Adopting a head feels like progress because the demo is warm. Stealing a pattern feels like homework because you must write contracts and move files.

Warm demos do not survive a laptop left at home, a vendor outage, or a policy incident. Contracts do.

I keep a replaceable-head charter for that reason. Sage can be plumbing. Another operator can plug in. The vault and MCP contract remain. That is not anti-tool. It is anti-hostage.

Failure modes

• Rewriting your world to match a Twitter screenshot
• Two sources of truth "temporarily"
• Persona prompts that speak as you externally
• Collecting harnesses like sneakers
• Skipping the export test because onboarding was pretty

A 48-hour steal drill

Hour 0-1: pick one external system you admire. Write the job in one sentence.
Hour 1-3: list five mechanics. Strike anything that requires their identity layer.
Hour 3-6: implement one mechanic on your files.
Hour 6-8: run the replaceability test (export, second head, or dry-run outage).
Next day: keep what survived. Delete the rest without guilt.

Closing

The market will keep shipping prettier heads. Let them. Your edge is a durable pattern library attached to judgment only you can authorise.

Steal the pattern. Do not adopt the head. Keep the vault. Own the send.