This directory now separates the current direction from archived brainstorming.
The archived documents are still important source material. They preserve the original Pitchfork and Pancakes design exploration, but they should not be treated as the current product direction unless a current doc explicitly carries an idea forward.
- Pitchfork System Overview: defines the full architecture across Pancakes, Pitchfork, identity, nodes, clients, projections, privacy boundaries, economics, and early build sequence.
- Pitchfork Ecosystem: defines the relationship between Pitchfork, Pancakes, the RPG client, and possible future clients.
- Pitchfork Privacy and Security: defines local-first sensitive data handling, permission boundaries, identity/access controls, event-stream privacy, backups, exports, AI boundaries, and phased security work.
- Pitchfork Data Sovereignty: defines data ownership, consent continuity, community governance, local/control requirements, anti-scraping rules, and secondary-use boundaries.
- Pitchfork Client API Spec: rough client-facing contract for nodes, identity, permission grants, events, settlements, projections, audit, exports, and security hard lines.
- Pitchfork Contracts: proposed reusable contract architecture for commitments, permissions, procedures, settlement, and governance.
- Understanding Pitchfork Contracts: explanatory companion to the contract architecture.
- Pitchfork Economics: defines the economic philosophy, social risks, capped symbolic rewards, cooperative pools, and real-money boundaries.
- Pitchfork RPG Client: defines the life-powered browser RPG concept, MVP loop, domains, resources, mentors, crafting, covenants, and long-term multiplayer direction.
- Pitchfork Household Management Model: defines how the Pancakes household model maps into Pitchfork events, covenants, resources, projections, privacy boundaries, and settlement rules.
- Pitchfork Roguelike: The Nexus: defines the Nexus as a projection-driven roguelike settlement layer for vendors, covenants, ledgers, factions, districts, and multi-client state.
- Ambient Symbolic Clients: defines symbolic environmental projection for Minecraft-like worlds, ambient clients, emotional ecology, and permissioned atmosphere.
- Pitchfork Node Quality of Life Signals: defines aggregate, ambient quality-of-life signals for node governance, support planning, fairness, and resilience.
- Legacy Carry-Forward: records which older mechanics remain useful and how they should be reinterpreted under the current direction.
- ChatGPT Export Inventory: tracks old transcript sources and what has or has not been mined from them.
- Pitchfork drafts: superseded Pitchfork and Mystical Mastery brainstorming around tokens, color magic, contracts, commodities, mentors, UI, stats, lore, and phases.
- Pancakes drafts: earlier Pancakes token and element experiments.
- Start with Pitchfork System Overview.
- Read Pitchfork Ecosystem for the broader Pancakes/Pitchfork relationship.
- Read Pitchfork Privacy and Security before implementing identity, permissions, cross-client sharing, sensitive clients, AI, exports, event streams, or analytics.
- Read Pitchfork Data Sovereignty before implementing consent, AI processing, research, aggregate data products, community data governance, or sensitive-client storage.
- Read Pitchfork Client API Spec before building any Pancakes or Pitchfork client integration.
- Read Pitchfork Economics before implementing markets, tokens, contracts, rewards, crypto, or anything with real-world value.
- Read Pitchfork Contracts and its explanatory reader before implementing commitments, procedures, enforcement, or settlement contracts.
- Read Pitchfork RPG Client before implementing gameplay.
- Read Pitchfork Household Management Model before implementing household events, household covenants, domestic resources, care rituals, or household projections.
- Read Pitchfork Roguelike: The Nexus before implementing settlement, vendor, faction, covenant-board, ledger-archive, or multi-client projection features.
- Read Ambient Symbolic Clients before implementing Minecraft-like, realtime, emotional ecology, environmental projection, or symbolic ambience features.
- Read Pitchfork Node Quality of Life Signals before implementing node-level aggregate metrics, public summaries, quality-of-life reviews, or support-planning dashboards.
- Use Legacy Carry-Forward when mining the archive for reusable ideas.
- Use ChatGPT Export Inventory when mining old transcript exports.
Pancakes product, node, governance, Lifecraft, service-exchange, and ecosystem doctrine documents are maintained in the Pancakes repository.
Current docs override archived drafts.
Archived mechanics can be reused when they support the newer principles:
- Human layer first.
- Symbolic before financial.
- Capped participation before tradable value.
- Crafting and contribution before raw behavior extraction.
- Privacy boundaries before cross-client data sharing.
- Local ownership and export before platform lock-in.
- Consent-based tools before ambient AI ingestion.
- Community governance before secondary use of community data.
- Covenants and cooperative support before speculative markets.