Status: Architectural Design
Pancakes is not intended to become a single application that attempts to do everything.
Instead, Pancakes is a family of applications built upon a common operational foundation.
Although these applications share capabilities, they exist to support different forms of human activity.
This document explains the relationship between three foundational Pancakes applications:
Together, these applications support most of the ordinary work through which people build lives, households, organizations, and communities.
People often perform a single real-world activity that simultaneously belongs to several domains of life.
For example:
A person bakes twenty loaves of bread.
That activity may be understood in several ways.
Within the household:
We have enough food for the week.
Within an enterprise:
Today’s production batch has been completed.
Within the service exchange:
Fresh bread is available for pickup.
Nothing happened three times.
Only one transformation occurred.
The applications simply emphasize different aspects of that transformation.
This principle appears throughout the Pancakes ecosystem.
Pitchfork records operational reality.
Applications present that reality through perspectives appropriate to human goals.
All Pancakes applications share common architectural layers.
People
↓
Pancakes Applications
↓
Node Capabilities
↓
Pitchfork
↓
Operational History
Applications should own user experience.
Node capabilities should provide reusable operational services.
Pitchfork should record canonical transformations and settlements.
No application should maintain an independent operational model when a shared capability already exists.
The Household application answers a simple question:
How do we live well together?
Its purpose is stewardship.
The household is not primarily a business.
It is a living system that transforms time, care, attention, and resources into safety, nourishment, belonging, resilience, and flourishing.
Accordingly, Household emphasizes:
Its primary concern is not maximizing productivity.
Its primary concern is maintaining continuity.
Examples include:
Household work often remains entirely private.
Many household recipes never leave the household node.
Enterprise answers a different question.
How do we carry out our undertaking well?
An enterprise may be:
Enterprise focuses on operational excellence.
Its concerns include:
Enterprise is concerned with how work is performed.
Whether the outputs are sold, donated, shared, or consumed internally is secondary.
A bakery and a community kitchen perform remarkably similar operational transformations.
Enterprise helps organizations perform them well.
Service Exchange answers another question entirely.
How do we help one another?
Unlike Enterprise, Service Exchange begins with relationships rather than production.
Its primary objects include:
Its focus is coordination between households, organizations, and individuals.
Service Exchange therefore introduces concerns that Household and Enterprise should not own directly:
These concerns arise whenever people exchange services across social boundaries.
The same activity may appear differently in each application.
Consider vacuuming.
Within Household:
Task
Vacuum the living room.
The goal is maintaining household continuity.
Within Enterprise:
Transformation
Restore a rental property to inspection condition.
The goal is operational completion.
Within Service Exchange:
Service
Offer house cleaning assistance to nearby households.
The goal is cooperation between people.
The activity is identical.
Its meaning changes according to context.
This distinction allows private household life to remain private while still supporting voluntary cooperation when desired.
These applications also represent different scales of participation.
A child may begin with Household.
They learn:
Later they begin tutoring classmates.
They use Service Exchange to advertise availability.
Eventually they establish a tutoring practice.
Enterprise becomes useful for scheduling, records, educational materials, and organizational continuity.
Nothing requires abandoning previous knowledge.
The applications evolve alongside the person’s life.
This reflects one of the core Pancakes design invariants:
People should not outgrow their tools.
Although the applications differ, they compose the same node capabilities.
Examples include:
Each application assembles these capabilities differently.
Household emphasizes routines and continuity.
Enterprise emphasizes procedures and operational history.
Service Exchange emphasizes coordination and trust.
The capabilities remain reusable.
A single application attempting to perform all three roles would become confusing.
Household users should not constantly encounter customer acquisition workflows.
Enterprise users should not manage production through chore lists.
Service Exchange users should not expose private household routines simply to request help from a neighbor.
Separating applications allows each to present concepts appropriate to its purpose while sharing a common operational substrate.
This separation improves clarity without sacrificing interoperability.
These applications are practical expressions of Lifecraft rather than separate philosophies.
Household primarily supports the practice of Hearthcraft, Carecraft, Heartcraft, and related domains by helping people steward daily life.
Enterprise supports the practice of Tradecraft, Civicraft, Truthcraft, and organizational stewardship by helping people transform effort into lasting institutions.
Service Exchange supports Carecraft and Civicraft by helping people discover opportunities for mutual aid, cooperation, and local economic participation.
Together they form complementary expressions of the same underlying philosophy:
People flourish by learning to care well for themselves, one another, and the institutions they build together.
Household, Enterprise, and Service Exchange are not competing products.
They are complementary perspectives on ordinary human life.
Household asks:
How do we live well together?
Enterprise asks:
How do we carry out our undertaking well?
Service Exchange asks:
How do we help one another?
All three observe the same operational reality.
All three share the same architectural foundation.
Each exists because people experience these forms of participation differently, even when they arise from the same real-world transformation.