pancakes

Pancakes Service Exchange

Purpose

Pancakes began partly as an app for mutual service exchange.

The original problem:

Overworked people often buy services from large companies because grassroots exchange with peers is hard to coordinate.

Pancakes can make informal care, household work, transportation help, tutoring, cooking, cleaning, errands, repair, and other ordinary services easier to exchange without forcing every exchange through a corporate gig platform.

Core Idea

Pancakes should support direct and indirect service exchange.

Direct exchange:

I cook for you.
You clean for me.

Indirect exchange:

I help one household.
I earn Pancakes credits.
I spend those credits later with another person or household.

The indirect model is important because it removes the need for perfect one-to-one reciprocity. A person can contribute where they are able and receive help from someone else later.

Tasks Are Not Services

Pancakes should distinguish personal or household tasks from Pancakes Earth services.

Tasks:

Services:

The same real-world action can be represented differently depending on context.

Example:

Task: Vacuum our living room.
Service: Offer vacuuming help to three nearby households.
Pitchfork interpretation: Gather Order Salt and reduce household entropy.

This separation matters because service markets create social and economic risk that ordinary private task tracking should not inherit.

Service Categories

Initial categories could include:

The old design also imagined reviving traditional or underrecognized professions as service identities:

This should be handled with respect. The point is not nostalgia for hierarchy. The point is to make useful local skills visible again.

Job Board

Pancakes can include a local job board.

Users can post:

Listings should support:

Pancakes Credits

Pancakes credits are a local accounting unit for service exchange.

Uses:

Credits should not start as real money.

Early credits should be:

The credit system should avoid pretending that every form of care has a perfect market price. Credits are coordination tools, not a complete theory of human value.

Rate Neutrality

Pancakes should avoid centrally pricing ordinary work.

The platform can define rules, units, caps, and safety boundaries, but it should not declare a universal exchange rate for “doing the dishes” or “vacuuming a carpet.”

Better:

Avoid:

For consistency, Pancakes can still define conversion rules between local credits and Pitchfork symbolic rewards. Those rules should be transparent, capped, and node-aware.

Baseline Credits and UBI

Earlier design explored a Universal Basic Income-like credit model.

Carry forward only as a cautious future direction:

This overlaps with Pitchfork’s symbolic basic income model. Any real-money version belongs behind the economic safeguards in Pitchfork Economics.

Family Accounts and Child Companion Mode

The early design imagined Pancakes as a parent or household companion and Pitchfork as a child-friendly magical layer.

Possible model:

Guardrails:

Subscription-linked mentor tokens were an early monetization idea. If used, they should be tied to the account or household, not multiplied by the number of children in a way that creates farming incentives.

Ratified Household Covenants

Household chores and care work can be represented as covenants.

A household node can ratify a covenant so it becomes recognized by that household’s local accounting rules.

Example:

Covenant: Keep the Kitchen Clear
Members: Alex, Sam
Promise: Dishes cleared after dinner three times this week.
Ratified by: Household Steward
Witness: Either member can attest; steward resolves disputes.
Reward: Household stability +2, Order Salt +1 each
Boundary: No public sharing outside the household node

Ratification means:

Prefer steward ratification for social approval. Use custodian for technical operation unless the same person holds both roles.

Domain-to-Essence Framework

The service exchange should eventually use the same domain mapping as Pitchfork.

Any domain can define:

Example domains:

This lets new domains plug into the same accounting substrate without forcing every domain into the same UX.

Pancakes Earth

Pancakes Earth is the geospatial layer of Pancakes.

It can show real-world service availability with strong privacy controls.

Possible features:

Examples:

Location data is sensitive.

Default rules:

BLE and Proximity

Mobile apps could use Bluetooth Low Energy for nearby discovery.

Possible uses:

BLE discovery should reveal the minimum necessary information.

Safer defaults:

Mesh and Local Infrastructure

The service exchange design connects to Pancakes nodes.

Earlier exploration imagined:

This remains useful as a distant infrastructure direction.

Near-term:

Later:

Pitchfork Integration

Pancakes credits can eventually connect to Pitchfork.

Possible integrations:

Guardrail:

Pitchfork should not turn real-world service work into uncapped game yield.

Pancakes credits and Pitchfork rewards should remain capped, transparent, and designed to avoid coercion.

Physical Tokens and Exchange Nodes

Earlier design explored physical Pancakes or Pitchfork tokens: for example copper rounds, silver rounds, serial-numbered objects, or redeemable artifacts.

This is distant future.

Useful idea:

If physical tokens ever exist, Pancakes needs exchange-node rules:

This should not precede a healthy internal credit system.

Anti-Gig-Economy Position

Pancakes should not become TaskRabbit with a friendlier skin.

Avoid:

Prefer:

Open Questions

Working Assumption

The first Pancakes service exchange should be local, simple, and non-speculative.

It should prove:

offer service
-> complete service
-> receive credit or recognition
-> spend credit or contribute to household/guild state

Only after that loop is healthy should Pancakes add broader federation, maps, BLE discovery, hardware nodes, cross-app credits, or real-money settlement.