Public book standards

This document explains what Rewrite the DNA must deliver and how contributors and readers can tell whether a chapter holds up. Editorial discussions and change ledgers stay outside the public repository.

Read the documents in this order #

1. outline.md defines the book's claim, locked terms, and chapter sequence.
2. This document defines what the book and each chapter must deliver.
3. prose-standard.md governs reader-facing prose.
4. chapter-template.md is the planning sheet.
5. The rewrite skill turns these documents into a workflow and does not introduce theory of its own.

When they conflict, follow that order. Repair a weak claim in the outline, repair thin evidence in the research, and repair only the sentence in the prose pass.

1. What a management book must deliver #

This book learns from the shared craft of Crossing the Chasm, The Innovator's Dilemma, Good to Great, The Lean Startup, Zero to One, and Blue Ocean Strategy. It does not copy their voice. Readers should leave with five things:

1. One counter-intuitive core claim — one sentence that evidence could disprove.
2. One reusable master framework — something readers can sketch on a whiteboard. Regenic uses Judgment × Context: unified judgment standards and shared context.
3. No more than five tier-one concepts — Rewrite the DNA / Regenic is the only outward lead concept. See outline.md for the full map.
4. Cases that test the claim — winners and losers; at least one external comparison per chapter, with an explicit missing side where evidence is incomplete.
5. An executable playbook — something a leader can start on Monday morning. Regenic uses the 90-day manual in Chapter 14.

Primary reader: the accountable leader: a founder, CEO, or business-unit head.

How the three carriers relate: the book is the current complete public argument; Regenic.ai is the living method; bioby.ai is the first experiment field, not the methodology homepage.

What Regenic does and does not do: it helps identify the limiting resource, encode standards, set acceptance criteria, and run a first validation cycle. It does not replace a leader's judgment, ghostwrite standards detached from the work, or promise to outsource the transformation.

2. Public naming #

• Primary title: Rewrite the DNA / Regenic
• Subtitle: How to Build an AI-Native Organization
• The Last Scarcity names the problem and titles the preface and Part II. It is a tier-two in-book concept, not a tier-one outward concept.

Title scoring and market tests are maintained outside the public repository.

3. What a finished chapter leaves behind #

Every finished chapter must satisfy all of the following:

1. It explains what it solves in the book, what it receives from the prior chapter, and what it hands to the next one.
2. Its claim can be restated in one sentence and advances the book's core claim.
3. It includes a whiteboard-ready framework.
4. It has at least one external winner/loser comparison with citable data; report medians separately for each side. A chapter may remain in draft with a declared evidence gap, but it cannot be marked complete without the missing side.
5. It leaves at least three lines worth testing as quotable candidates, without forcing them into the body prose.
6. It ends with a "what to do Monday morning" action list.
7. Its body paragraphs pass prose-standard.md: the argument is accurate, the causal chain is clear, and the prose reads like a person explaining rather than a standard issuing instructions.

4. How to divide writing and verification time #

• 10% standards: read this file, outline.md, and prose-standard.md; confirm what the chapter must do.
• 10% evidence: assemble public research and the private case library. Internal cases cannot be the only evidence.
• 80% drafting, verification, and revision: write a one-page brief, test the logic, expand the chapter, then rewrite body prose against the prose standard.

Chapter state: one-pager → drafting → complete → open public revision.

5. How to tell whether it is working #

Over time, ask three questions: do the core concepts become organizational language; how many teams finish a first cycle with the standards; and does Regenic.ai keep publishing checkable success, failure, and applicability cases?

See /en/versions for public revision history.