Status: Draft Character: Foundational Design Document
This document defines Recipes as the primary lifecraft primitive used throughout the Pancakes ecosystem.
Pancakes is not fundamentally a task manager, productivity system, or habit tracker.
Pancakes is a system for helping people cultivate flourishing across the domains of life that matter most:
Recipes provide the primary structure through which these transformations are described, taught, practiced, and shared.
Most software organizes life around tasks.
Do Laundry
Buy Groceries
Schedule Appointment
Pay Bill
Tasks are useful.
But they are often too small to capture what people are actually trying to accomplish.
For example:
Task:
Do Laundry
is not the real goal.
The real goal is:
Maintain Clothing Continuity
Similarly:
Task:
Buy Groceries
is usually part of:
Maintain Food Continuity
And:
Task:
Pay Electricity Bill
is usually part of:
Maintain Household Stability
Human flourishing depends less on isolated tasks and more on ongoing transformations that preserve continuity and create conditions for growth.
Recipes provide a way to model those transformations.
Pancakes views life as a collection of recurring transformations.
Events
→ Activities
→ Recipes
→ Continuity
→ Flourishing
Events are individual occurrences.
Activities are specific actions.
Recipes organize activities into meaningful transformations.
Flourishing emerges from repeated successful transformations across multiple domains of life.
A recipe is a reusable description of a meaningful life transformation.
Examples include:
Recipes describe:
Recipes focus on transformation rather than compliance.
Conceptually:
recipe:
id:
name:
purpose:
participants:
ingredients:
process:
settlement:
outputs:
privacy_boundary:
This structure is intended to guide design and implementation rather than constrain human practice.
Purpose explains why a recipe exists.
Examples:
Maintain household continuity.
Improve sleep quality.
Strengthen family relationships.
Develop budgeting skills.
Purpose helps distinguish meaningful transformation from mere activity.
Participants identify who is involved.
Examples:
Some recipes are personal.
Others are collaborative.
Many household recipes involve multiple participants, even when one person performs most of the visible labor.
Ingredients are resources required for transformation.
Examples include:
Not all ingredients are physical.
Many important transformations depend upon emotional, relational, or cognitive resources.
The process describes a suggested path.
Unlike traditional workflows, Pancakes recipes are not rigid instructions.
They are adaptable patterns.
Different households, cultures, communities, and individuals may perform the same recipe differently.
For example:
Recipe:
Family Meal
may be realized through very different practices in different households.
The purpose and settlement matter more than strict procedural conformity.
Settlement defines how participants know the transformation has occurred.
Examples:
Meals planned for the next seven days.
All household members have sufficient clean clothing.
Family meeting completed.
Monthly budget reviewed.
Settlement focuses attention on outcomes rather than activity counts.
Outputs are what emerge from successful transformation.
Examples:
Outputs are often intangible.
This is intentional.
Many of the most important forms of value in human life are difficult to measure directly.
One of the central insights behind Pancakes is that much of life consists of continuity work.
Examples:
Much of this work is invisible.
Many household management systems focus on tasks while ignoring the continuity those tasks sustain.
Recipes help make continuity visible.
A major motivation for the recipe model is recognition of invisible labor.
Examples include:
These forms of labor often create the conditions that allow visible work to occur.
Recipes provide a structure for acknowledging and teaching these practices without reducing them to productivity metrics.
Pancakes supports recipes across all major domains of life.
Household recipes maintain continuity within homes and families.
Examples:
These recipes make invisible household management visible.
Health recipes support physical and mental well-being.
Examples:
These recipes focus on sustainable well-being rather than optimization.
Relationship recipes support connection and belonging.
Examples:
Relationships are cultivated through practice.
Recipes help make those practices visible.
Learning recipes support growth and skill development.
Examples:
These recipes transform effort into competence.
Financial recipes support stability and stewardship.
Examples:
The goal is financial resilience rather than financial maximization.
Community recipes support participation beyond the household.
Examples:
These recipes strengthen social fabric.
Governance recipes support collective decision making.
Examples:
Governance is treated as a form of collective lifecraft.
Recipes are the primary educational unit within the Pancakes ecosystem.
Mentors teach recipes.
Mentors do not primarily assign tasks.
Instead, mentors curate practical wisdom.
Examples:
Mentors help participants develop mastery through practice.
Recipes may build upon one another.
Examples:
Meal Planning
↓
Shared Cooking
↓
Hospitality Gathering
or:
Sleep Preparation
↓
Consistent Sleep Routine
↓
Recovery Practice
Recipe graphs create learning journeys rather than isolated activities.
Recipes are individual transformations.
Grimoires are collections of recipes and related wisdom.
Examples:
People typically interact with grimoires rather than isolated recipes.
Grimoires preserve and transmit accumulated knowledge.
Pancakes recipes describe meaningful transformations.
Pitchfork covenants coordinate and settle transformations when coordination is required.
Examples:
Recipe:
Weekly Meal Planning
may remain entirely private.
However:
Recipe:
Household Review
might become:
Covenant:
Quarterly Household Review
when multiple people agree to participate.
Not every recipe requires a covenant.
Most recipes remain entirely within the Pancakes layer.
The goal is care, continuity, and flourishing.
Not task completion metrics.
Recipes emphasize outcomes rather than isolated activities.
Human flourishing cannot be reduced to efficiency.
Recipes should teach judgment rather than enforce rules.
People should remain in control of their own lives and data.
Recipes should be adaptable to different households, cultures, and communities.
Recipes are the foundational lifecraft primitive of the Pancakes ecosystem.
They provide a way to describe, teach, practice, and share meaningful life transformations.
Recipes help make invisible forms of care visible.
They preserve practical wisdom.
They support continuity.
They create pathways toward flourishing.
Pancakes is not a task manager.
It is a lifecraft system.
Recipes are how lifecraft is practiced.