The Pancakes ecosystem is intentionally organized into architectural layers.
Each layer has a distinct responsibility.
This separation helps keep concepts cohesive, avoids duplicate definitions, and allows individual projects to evolve without redefining the entire ecosystem.
This document provides a high-level architectural map of the ecosystem and identifies the canonical home for major concepts.
The Pancakes ecosystem is not a single application.
It is a collection of interoperable systems built around a shared philosophy of human flourishing, stewardship, local autonomy, and non-exploitative infrastructure.
Rather than organizing documentation by software component, the architecture is organized by responsibility.
Each layer builds upon the one below it.
Each concept should have one canonical home.
Human Flourishing
│
▼
Commonwealth
│
▼
Nodes
│
▼
Capabilities
Reference Services
│
▼
Identity & Permissions
│
▼
Pitchfork
│
▼
Settlement
Contracts
Recipes
Projections
│
▼
Clients
│
▼
Networks
Information generally flows downward.
Experience generally flows upward.
The highest layer defines why the ecosystem exists.
It answers questions such as:
Representative documents include:
This layer defines principles rather than implementation.
The Commonwealth layer defines how people organize together.
Topics include:
Representative documents include:
This layer explains social organization independently of technical implementation.
Nodes are the operational units of the ecosystem.
A node is simultaneously:
Nodes may represent:
Representative document:
Nodes host reusable runtime services that support every client.
These include:
Representative documents include:
These services provide shared infrastructure without imposing application behavior.
Pitchfork is the ecosystem’s shared symbolic and accounting substrate.
Pitchfork is responsible for:
Pitchfork deliberately avoids becoming a general-purpose application platform.
Representative documents include:
Clients present different interpretations of the same underlying activity.
Examples include:
Clients own:
Clients do not redefine accounting or governance.
They interpret them.
Networks describe relationships between nodes.
Networking is not required for a useful Pancakes deployment.
Instead, networking allows independent communities to cooperate while retaining local autonomy.
Topics include:
Representative document:
Networking extends local systems.
It does not replace them.
Several concerns intentionally span multiple layers.
Privacy begins with human dignity.
It continues through governance, permissions, accounting, networking, and user interfaces.
Privacy is therefore a design principle rather than a single subsystem.
Stewardship appears at every level.
People steward households.
Communities steward common resources.
Nodes steward data.
Capabilities steward services.
Applications steward user experience.
The ecosystem treats stewardship as a recurring pattern rather than a single feature.
Every layer should support meaningful local operation.
Networking, federation, and hosted infrastructure expand local capability rather than replacing it.
A single person running a single node should still possess a complete and coherent system.
Every significant architectural concept should have one canonical definition.
Other documents should reference that definition rather than creating alternative versions.
This keeps the ecosystem internally consistent as it grows.
Readers unfamiliar with the ecosystem should generally progress in the following order:
This sequence moves from purpose to implementation while preserving the relationships between layers.
The Pancakes ecosystem should feel like a collection of well-defined layers, each with a clear responsibility.
The purpose of layering is not abstraction for its own sake.
It is to ensure that: