You Already Have a Second Brain. It’s in Your Sent Folder.
I’m the Film Commissioner for the Florida Keys. 42 bridges. 10 state parks. 2 national parks. 1 national marine sanctuary protecting the only living coral barrier reef in North America. 120 miles of islands, each with its own personality and its own rules.
A lot of what I know lives in my head. How to get a film permit in Key West. What the National Park Service wants before you can bring a crew to the Dry Tortugas. Why a traffic control request on the Seven Mile Bridge goes to the Monroe County Sheriff, and the same request on Duval Street goes to Key West PD, because those are two different jurisdictions and two completely different conversations.
Nobody wrote that down. I just know it because I’ve been doing this for eight years. When a producer texts me at 11pm and I’m a few drinks deep on Duval Street, memory is a bad system for a complicated job.
For years I wanted a knowledge base. I’d sit down with coffee, open a new document, title it something ambitious like “Florida Keys Film Office Knowledge Base v1,” and stare at the blinking cursor. Five minutes later I’d close the tab and go answer an email instead. The blank page won every time.
Then one afternoon I was drafting a reply to a producer asking about permits for Bahia Honda. I started typing out the process. State park, DEP jurisdiction, contact the park manager directly. Halfway through, I stopped.
I’d written this email before. A dozen times. To a dozen different producers.
The blank page wasn’t blank. I’d been writing the knowledge base for years. I’d just been emailing it instead of filing it.
What I actually found
I fed eight years of sent email to Claude and asked it to pull out the patterns. Here’s a sample of what came back.
The state park workaround. Permits to film at Bahia Honda or Fort Zachary Taylor route through DEP in Tallahassee. That’s the official process and it’s slow. What actually works is calling the park manager first. Cass at Bahia Honda. Andrew at Fort Zach. Get them bought in on what the production wants to do, and the Tallahassee paperwork becomes a rubber stamp instead of a negotiation. I’d explained that logic to producers for years. I never wrote it down as a principle anywhere. Claude pulled it out of my replies.
The FDOT drone rule. When a production wants to fly a drone near a state bridge, the FAA wants a flight diagram, a Part 107 certificate, and a specific callout that the drone flies parallel to the highway, not over it. There’s a specific person at the South Florida FSDO whose name belongs in every one of those emails. I’d been rewriting that instruction from memory every time it came up. It was already in my outbox.
The COI rejection pattern. Productions get their certificates of insurance bounced for the same five reasons. Wrong legal name. Expired dates. Missing NAIC on Workers Comp. Missing FDOT endorsement. Jurisdiction not listed as additionally insured. Every time one got rejected, I explained why in an email. I never compiled the list. Claude did. Now I send new productions the checklist up front, and the COI comes back correct the first time. The back-and-forth is gone.
None of that was in a document anywhere. It was scattered across hundreds of replies to producers, location managers, and county attorneys. It was the knowledge. It just wasn’t the knowledge base.
What the sent folder gets right
Starting from scratch means trusting your memory to surface the right things in the right order. Your memory won’t do it. Mine didn’t.
Sent email is written under the pressure of an actual question. Someone needed the answer. You gave it to them. The language is real. The details that mattered are the ones that ended up in the reply because they mattered to the person asking.
Eight years of that is an archaeological record of what you actually know, written in the moment, for people who needed it.
What it changed
Here’s what the workflow looks like now. A permit inquiry comes in. I drop it into Claude, which has the knowledge base loaded as context. Claude drafts a response in my voice, with the right details, routing the production to the right people. I read it, tighten what needs tightening, and send it. An hour of work becomes five minutes.
Sometimes Claude gets something wrong. It misses a nuance. It pulls an outdated detail. I correct it in the conversation, Claude notes the fix in the knowledge base, and the correction sticks. Next time the same question comes up, the right answer is already there. The system corrects itself as you use it.
If I get hit by the Conch Train tomorrow, the next person walks into a database of how things actually work in the Florida Keys, written by someone who did the job. That didn’t exist a year ago. Now it does. I didn’t write it. I excavated it.
Try it
Export your sent email from the last two years. Drop it into a Claude conversation. Ask it to identify the topics you write about most often, the recurring explanations, the patterns in how you answer specific kinds of questions.
You’ll find things you forgot you knew. You’ll probably find a system you’ve been running intuitively for years and never articulated. You might find the answer to a problem you’re working on right now, already written by you, to someone who asked at exactly the right moment three years ago.
The knowledge base isn’t something you have to build.
You just have to dig.
