The named framework rule, and why every Crazy Simple book has one

Every Crazy Simple Press title publishes with a named framework inside it. Not a list of tips. Not a collection of principles. A model with three to five distinct pillars and a name the reader will repeat back to a colleague.

This is not a stylistic preference. It is the structural condition that separates books that get cited from books that get shelved after one read.

What a framework actually is

A framework is the repeatable answer to the question your reader came to ask. It has pillars because a reader cannot operationalize a single idea across thirty chapters without a scaffold. It has a name because names travel. A reader who finishes your book and tells a peer about it will either say "you should read this" or "you should try the Reciprocal Loop." One of those recommendations generates a sale. The other generates a bookmark.

The framework also holds the manuscript together architecturally. Every chapter connects back to one of the pillars. The named framework is what prevents the book from becoming a loose collection of smart essays that the reader finishes without knowing what to do next.

What a framework is not

A framework is not a rebrand of common knowledge. "Assess, plan, execute" is not a framework. It is a sequence every reader already owns. The test is whether your specific pillars could only have come from your specific experience in your specific category. If a competitor could build the same diagram with different color blocks, the framework is not ready.

Name it when the pillars earn the name. The editorial team reviews your Framework Draft in Step 2 before the project moves to Step 4. If the framework needs work, you get notes and a path to resubmission. The gate is not a rejection. It is a quality hold.

Why we will not waive it

Authors occasionally push back on this requirement, usually in week two. The argument goes: my readers do not need a framework, they need my stories and my experience and my voice. That argument is correct about what readers want. It is wrong about what readers retain.

A story without a framework lands as anecdote. Readers love it in the moment and cannot recall the point three weeks later. A story inside a framework lands as evidence. The reader comes back to it when they face the same situation in their own work.

The framework is not decoration. The framework is the reason the book still works twelve months after launch, when a new reader finds it and needs to trust it without knowing you personally.

Name the thing. Do it clearly. The book compounds from there.