Colophon

The Cookbook began with a research phase. Four lines of inquiry ran side by side: what know.sh does today, read from its code rather than its plans; how people make study guides, syllabi, cookbooks, Bible studies, series bibles and ninety-odd other kinds of reference now, and what goes wrong for them; how the best use-case galleries and cookbooks are built; and what a responsible recipe has to say about copyright, academic integrity, health, law, money, faith and food. Nearly a hundred candidate uses came back with evidence of real demand. The fifty here are the ones with a finished result people recognise, at least three parts of know.sh doing real work, and no caveat so heavy it swamps the recipe.

Every recipe follows the same rules. It promises only what know.sh does now: no export, no uploads, no teams, one owner per library, public links that are read-only and one document wide. It is written for whichever assistant the reader already uses, connected through MCP, and it shows that assistant as a clerk and researcher, never a ghost-writer. It says where it falls short. Where the subject calls for it, it carries a note: quote Bible translations within their permissions, list allergens and cook to safe temperatures, keep health, children’s and clients’ information off public links, and treat AI summaries as leads to check rather than sources to cite.

The specimens are illustrations written for this book and set in the app’s own type. The people, families, congregations and companies in them are invented, and no recipe is a testimonial.