Status: Exploratory design notes
This document explores possible architectures for recognizing and settling valuable contributions within Pancakes Service Exchange.
Unlike the Pancakes economic theory documents, this document intentionally remains speculative.
The purpose is not to define the architecture.
The purpose is to explore the design space.
The simplest mental model looks like this.
Node A
↓
records activity
↓
Node B
↓
pays for activity
For example:
Cook dinner
↓
10 credits
This resembles a conventional labor market.
It is easy to understand.
It is also probably the least interesting possibility.
It reduces Service Exchange to gig work.
Perhaps the wrong thing is being exchanged.
Activities are individual events.
Capabilities are demonstrated patterns.
Preparing one meal is an activity.
Being capable of sustaining household nutrition for six months is a capability.
This distinction feels important.
Instead of becoming economic transactions directly, activities accumulate into evidence.
Cook meal
↓
Recorded activity
↓
Household Nutrition evidence
↓
Capability
The capability becomes the economically interesting object.
Capabilities need not be professional credentials.
Examples include:
Most of these have no conventional labor market despite producing substantial social value.
Perhaps communities do not purchase activities.
Instead they recognize demonstrated capability.
For example:
Community Kitchen
Recognizes:
Household Nutrition
Requirements:
100 qualifying meals
over at least 60 days
Recognition:
250 community credits
The organization is not buying meals.
The meals already happened.
The organization is recognizing demonstrated stewardship.
This observation may be one of the most important.
Traditional labor markets assume:
buyer
↓
seller
Household labor frequently lacks an identifiable buyer.
The beneficiary may be:
The value exists.
The purchaser does not.
This suggests that conventional labor market assumptions may be the wrong foundation.
Households generate many public goods.
Healthy children.
Healthy adults.
Stable neighborhoods.
Volunteer capacity.
Reduced healthcare utilization.
Community resilience.
Future caregivers.
Future workers.
These benefits extend beyond the household itself.
Perhaps communities therefore have legitimate reasons to recognize household stewardship.
Instead of publishing prices, organizations could publish recognition programs.
Examples:
Women's Cooperative
Recognizes
Sustained Caregiving
Benefits
Emergency grants
Transportation
Education support
Food Bank
Recognizes
Household Nutrition
Benefits
Leadership opportunities
Volunteer stipends
Neighborhood Association
Recognizes
Community Stewardship
Benefits
Tool library access
Garden funding
Microgrants
No one purchases cooking.
Cooking becomes evidence.
Perhaps Service Exchange is fundamentally misnamed.
Perhaps services are not exchanged.
Capabilities are.
Organizations publish:
We recognize these capabilities.
Households publish:
We possess these capabilities.
Settlement follows.
Importantly, capabilities should not require exporting activity histories.
Instead:
Organization requests proof.
Node proves capability.
Activity history remains local.
For example:
Requested capability
Household Nutrition Level 2
↓
Proof generated locally
↓
Capability verified
↓
Settlement
This aligns naturally with Pancakes’ commitment to data sovereignty.
One capability may be valuable to many organizations simultaneously.
Household Nutrition
↓
Women's Cooperative
↓
Food Bank
↓
Community Kitchen
↓
Mutual Aid Network
↓
Faith Community
Each organization establishes its own recognition policy.
No central authority determines value.
This architecture resembles Hayek’s value discovery.
Organizations independently publish what they value.
Communities independently decide what to recognize.
Households independently choose what evidence to disclose.
Settlement emerges from interaction rather than central planning.
One consequence deserves particular attention.
Historically, invisible labor often produces no independent assets.
Capability recognition changes this.
Invisible labor
↓
Evidence
↓
Capability
↓
Recognition
↓
Settlement
↓
Personal assets
This creates agency.
Participants gradually accumulate resources under their own control.
One compelling application involves domestic abuse.
Years of invisible household work often produce little independent economic security.
Recognition programs could gradually accumulate privately controlled resources.
The purpose is not to encourage household dissolution.
The purpose is preserving meaningful exit options.
Institutions should increase the range of futures available to participants.
Settlement need not always involve money.
Possible forms include:
Money is only one possible settlement mechanism.
Traditional markets resemble:
buyer
↓
seller
↓
price
Capability settlement may instead resemble:
contributors
↓
capabilities
↓
communities
↓
recognition
↓
settlement
This feels less like a labor market and more like an ecosystem of institutions.
Many questions remain unanswered.
Should capabilities be standardized?
Who defines capabilities?
Can communities define their own?
How are capabilities updated?
Can capability requirements evolve?
Can organizations revoke recognition?
Should settlements recur automatically?
Can organizations sponsor capabilities?
Should capability proofs be anonymous?
Can one activity contribute to multiple capabilities?
Can capabilities expire?
Should communities publish capability “bounties” rather than prices?
This document builds upon:
Unlike those documents, this one remains intentionally exploratory.
The concepts presented here should be treated as hypotheses rather than architecture.
Future work may demonstrate that capability settlement is the correct abstraction—or reveal an even better one.