Foundations · Chapter 01
Why a living textbook
Capability moves faster than print. The book has to re-test itself every week.
A book that maintains itself. Each week new research is checked against every hypothesis, and each one is marked holds, stressed or changed. Changes are published in the changelog. The book applies its own method to itself: a fact layer, a set of claims under test, and rules for what changes and who signs off. Glossary ↗
A book about autonomous businesses has an unusual problem: the tools it describes can change while someone is reading it. A recommendation that made sense when a chapter was written may need a different boundary, a different test or a different tool a few months later. Keeping the words available is not the same as keeping the advice useful.
The answer proposed here is to give the book the same structure it asks a business to build. Its definitions provide a shared model. Its hypotheses make the claims explicit. Research supplies evidence that can support those claims or force their revision. The reader should be able to follow the argument without opening those records, but the records should be there when they want to question it.
How the book updates itself
The review begins with new research and tools collected in an inbox. Each item is read against the hypotheses it might support or challenge. The useful question is not simply whether a paper is interesting, but whether it changes a decision the book advises someone to make.
A finding becomes a proposal before it becomes published text. The proposal names the claim, the evidence and the reason for changing it. Automation can help collect and compare material; the operator remains responsible for approving a publication decision. A proposal can be accepted, rejected or returned with a clear account of what is missing.
When a revision is accepted, the earlier wording stays in the record alongside the new version. The Hypothesis Diff is intended to carry that account to readers: what holds, what is stressed, what changed and which tools are worth trying. The whole-book changelog keeps the same record available between emails.
The record matters as much as the update
A working review process leaves evidence of its own work. Each live hypothesis has a recent review date, each change can be traced to its sources and approver, and a returned proposal comes back with the missing work addressed. A page that merely changes its date has not met that standard.
This edition is a saved snapshot. Its hypotheses and their falsifiers are editorial drafts, and the weekly review process described here is not yet automated. The distinction matters: publishing the method makes it possible to judge the book by it, rather than treating a promise to stay current as proof that it does.
Read the book with one real piece of work in mind. Choose an outcome you care about, record how the work happens today and follow its dependencies through context, procedure, access, evaluation and operation. Build only what that outcome needs. The value of a living book is that its advice can change as you learn what works in your business.
Tools and setup
Prior work: David J. Bland and Alexander Osterwalder's Testing Business Ideas supplies a disciplined approach to testing assumptions. Our setup sequence adapts that principle to operating workflows; it is not their published curriculum.
- Choose an existing private document home. Create a register with page, outcome, owner, evidence link and status: planned, tested, blocked or active. These are suggested fields, not a built-in Notion template.
- If using an assistant with Notion, follow Notion's MCP setup: use Settings → Notion MCP or the assistant's supported integration flow; authenticate the intended workspace. Review actual access before connecting.
- Ask it to retrieve one known test page. Compare its title and content with the original. Approve a harmless draft write separately; retrieve it again. This verifies that specific action, not unattended execution.
Setup paths checked against linked documentation on 15 November 2026. Verify current account support during setup; reader integrations have not been tested here.
Work through this with your agent
Paste the request into your assistant. It will interview you and help produce the working artifact.
Act as my autonomous-business setup partner. Start interviewing me now, at most three short questions per turn, and wait for answers. Ask what my business sells, who buys it, and which recurring outcome I want to improve. Inspect existing artifacts I authorize you to read; reuse completed work. Select the smallest useful path through: workflow choice, personal context, company facts, capture, data, skills, connections, evaluation, execution, economics, delivery, demand, growth and operating review. Explain which steps are needed now and which can wait. Give every selected step an owner, input, output and observable completion check. Agree a destination before saving files; preserve existing content. Keep a progress register linking actual artifacts and evidence. Label planned, tested, blocked and active separately. Do not activate automations or make consequential external changes without approval of the specific action. Finish with one next interview command to run, not a shopping list of products.
Use these documented setup paths as references; check current account support before acting:
https://www.strategyzer.com/library/testing-business-ideas-book
https://www.notion.com/help/notion-mcp