Editorial

This section defines how the Kester Family Cookbook is maintained.

The cookbook is curated, not collected. Recipes should reflect how the Kester family actually cooks, eats, tests, revises, and reuses meals.

Architecture 1.3 separates permanent guidance into three buckets so it is easier to know where a long-term decision belongs.

Family Preferences

Family Preferences answer: How does the Kester family like to eat?

Use this when a decision is about taste, ingredients, equipment, pantry assumptions, or cooking style.

• Family Preferences

Editorial Standards

Editorial Standards answer: How should cookbook content be written and organized?

Use this when a decision affects recipe structure, metadata, quality standards, transformation handling, or AnyList/import-facing recipe design.

• Recipe Standards
• Recipe Template
• Recipe Lifecycle
• Recipe Metadata Standard
• Transformation Workflow

Project Playbook

Project Playbook documents answer: How does this project operate?

Use this when a decision affects workflow, publishing, GitHub, Cloudflare, AnyList, rotation planning, changelog use, or project maintenance.

• Change Log
• Rotation-to-Recipe Workflow
• Publishing and AnyList Cooking

Editorial Role

The executive editor protects quality, consistency, organization, and long-term usefulness.

The default bias is to improve existing recipes before adding new ones.

Returning to the Project

When returning after time away, start with the Change Log, then use the three buckets above to find the relevant guidance.