Someone accused me this week of using AI to write my content.

They meant it as an insult. I’m going to take it apart as a frame, because the accusation itself is the tell — and the tell is worth naming publicly for every operator and consultant in this feed who’s watching the same pattern play out against their own work.

The Accusation And What It Actually Reads As

The accusation runs like this: the writing is too dense, too fluent, too consistent, too fast. Nobody produces this much material at this level without a machine writing it. Therefore, machine.

That’s the surface argument. What it actually reads as, once you run it through, is this: the accuser doesn’t have a model for what 44 years of accumulated framework work looks like when the operator finally opens the taps.

I’ve been in the restaurant business for 44 years. Twenty-two of those years running operations directly. Twenty-two of those years consulting with operators. Somewhere in the neighborhood of 150 restaurant openings. Every one of those years I was taking notes, writing articles, drafting frameworks, naming patterns, and building the vocabulary I now use to teach the operating physics of this business.

The corpus was already there. What changed is when I decided to publish at the pace the framework had been accumulating at for four decades.

That’s not AI writing. That’s an operator running a refinement pass on his own body of work.

Why The Pace Changed

I did not always write at this pace. Before COVID, I documented my work in fits and starts. I published when I had time. I let entire framework decisions sit as notes in a folder because I assumed I had time to formalize them later.

Then I lost my son, my mother, and my father in the same year.

That year rearranged my read on time. I decided that whatever life I had left, I was not going to spend it on superficial arguments that never went anywhere. I was not going to spend it in street fights with people who were a waste of my time. I was not going to spend it hedging positions I already knew were correct to make industry counsel comfortable.

I decided my life’s work was worth enough to me that I owed it my time — and I owed my time to the operators the framework was built to help.

That is the decision that changed the pace. Not AI. A decision, made in the aftermath of loss, that the framework was going to get published and the arguments were going to get taken seriously by an operator who no longer had time for the alternative.

Why The Register Changed

The other read on my writing right now is that it does not sound like most social media writing. That is correct. It doesn’t.

I’ve always been a serious, formal writer. That is my native register. What happened over the last decade of social media is that I let the register drift. I got into fights I should not have been in. I engaged with commenters whose only goal was to be seen engaging with me. I allowed the platform to pull my writing toward the platform’s mean, which is short, reactive, and shaped by whoever was loudest that day.

That is over. When I decided to publish the framework in full this year, I decided to publish it in the register the framework deserves — direct, load-bearing, unhedged, and grounded in decades of successful experience running and consulting to real restaurants.

I am educated. I have four decades of results. I have positions on the record that I built the hard way. I owe those positions the register they were built in. I do not owe the platform a softer version.

That is not AI writing. That is a decision about what my writing is for.

What AI Actually Does For Me

Here is what AI does in my workflow, precisely:

It reads the corpus faster than I can. When I’m drafting a new piece and I want to know whether I’ve already published a position on a specific point, AI can run semantic search across 1,600+ documents in my knowledge base in seconds. That’s not writing. That’s retrieval.

It flags casing violations and vocabulary drift. My framework runs on a locked lexicon — specific bracketed IP terms with canonical casing that has to match across every surface. AI catches when I’ve written a term wrong. That’s proofreading, not authorship.

It surfaces family relationships between terms. When I’m working on a new dictionary entry, AI can pull every related, opposing, and parent term from the corpus and hand me a list of what needs cross-referencing. That’s indexing, not thinking.

It runs pushback against my drafts. When I want to know whether a position I’m taking will hold up under a specific counter-argument, AI can run the counter-argument at me hard. I decide whether the position holds or needs revision. That’s editing, not writing.

It converts formats. Markdown to HTML. Long-form to teaser. Article to KB entry to LinkedIn post. That’s typesetting, not creation.

What AI Cannot Do In My Workflow

Every one of the above is a labor multiplier on work I’m already doing. None of them produces a framework. None of them writes a load-bearing piece. None of them has an operator’s read on a specific problem.

Here’s what AI cannot do:

It cannot name a mechanism that isn’t in its training data. Every load-bearing IP term in my framework — Operator Arbitrage, The Guest Contract, Road Cancer, Framework Arbitrage, Symbolic Price Equity, Edison Trust Arbitrage, Case Study Reduction — is a term I named because I saw the mechanism operating in real restaurants and no existing vocabulary named it correctly. AI can restate a term I’ve defined. It cannot originate one.

It cannot hold a position under contradiction. My framework takes positions that contradict industry counsel across half a dozen dimensions. Every one of those positions is a decision I made after running the mechanism against real operations for years. AI does not have those years. It has statistical adjacency to industry counsel, which is exactly the wrong data set for taking positions against it.

It cannot read a specific operation. My core consulting work — the Diagnostic, the PeriodReview, the OnsiteReview — is running framework-level reads on live operations. AI has never worked a shift. It has never watched a lead break under a Guest Contract violation. It has never seen a cast member fork. It has never sat across a table from an operator whose numbers are collapsing and whose Perspective is the actual constraint. That work is not writeable by anything that hasn’t done it.

It cannot generate coherence across 1,600 documents. Every entry in my knowledge base cross-references every other relevant entry in the corpus. Every position I take on the blog reinforces positions I take in the books. Every diagnostic test in a fieldbook maps to a mechanism in the parent book. That coherence is not an AI output. That coherence is the framework itself, and it was built one decision at a time over decades.

The Real Read On The Accusation

When someone accuses an operator or a consultant of using AI to write their content, one of three things is running underneath:

They don’t have a model for volume plus coherence. They see the pace, they see the density, and they don’t have a category for “this person has been building this for forty years and just started publishing at scale after deciding his time was worth spending on it.” Machine is the only explanation their model can produce.

They read register-density as inauthenticity. Most industry writing is soft, hedged, and consensus-shaped. When they see writing that is direct, load-bearing, and unhedged, it feels foreign. Foreign gets labeled machine.

They read a position they can’t respond to and reach for the easiest dismissal. “AI wrote it” is faster than “he’s right and I don’t have a counter-argument.” The accusation is a way of not engaging with the substance.

I don’t know which of the three was running in the accusation I got this week. It doesn’t matter. The frame is the same in every case: the accuser doesn’t have a model for what a real operator, running a real framework, doing real work at scale, actually looks like.

What This Means For Every Operator In This Feed

If you are building a body of work in the restaurant business — or in any business — and you are running your own framework, taking your own positions, and publishing at the pace your accumulated work allows, you are going to get this accusation. It’s coming. It might already have arrived.

The move is not to defend yourself against it. The move is to keep publishing.

The accusation is a symptom of the industry not having a category for what you’re doing. You do not owe the industry a category. You owe your operators the framework.

I use AI the way an operator uses a saute pan — as a tool that lets me execute work I’ve already designed. The design is mine. The framework is mine. The 44 years are mine. The reads are mine. The positions on the record are mine.

The pan doesn’t cook. The operator does.