90 lines
5.1 KiB
Markdown
90 lines
5.1 KiB
Markdown
# MEA × rSpace-Online: Executive Summary
|
||
|
||
> Analysis of the Mycelial Economics (MEA) framework in the context of
|
||
> rSpace-Online's existing collaborative tools and what they can already provide.
|
||
|
||
---
|
||
|
||
## Overview
|
||
|
||
The **Mycelial Economics (MEA)** framework is a protocol-based economic coordination
|
||
system built around small, bounded groups ("Pods") that grow through division (mitosis),
|
||
maintain intentionally sparse inter-pod relationships, and use a gradient-based exchange
|
||
protocol tied to relational distance.
|
||
|
||
After a thorough review of the 104-page MEA document and rSpace-Online's 35-module
|
||
ecosystem, the conclusion is clear: **rSpace already covers ~70% of MEA's core
|
||
infrastructure requirements.** The architectural alignment runs deep — both systems
|
||
share the same first principles.
|
||
|
||
---
|
||
|
||
## Direct Matches (No Changes Needed)
|
||
|
||
| MEA Concept | rSpace Module | Notes |
|
||
|---|---|---|
|
||
| **Self-sovereign identity** | **EncryptID** (WebAuthn/DID) | Exactly what MEA specifies — no central authority, passkey-based, DID ownership |
|
||
| **Offline-first data sync** | **Automerge CRDT** | Layer-for-layer match with MEA's 4-tier data architecture (device → server → shared → federated) |
|
||
| **Bounded groups (Pods)** | **Spaces** | Collaborative containers with member lists, roles, nested hierarchy, permission cascading |
|
||
| **Governance** | **rVote + rGov + rChoices** | Voting, proposals, quorum, multi-criteria decisions — covers pod-internal decision-making |
|
||
| **Payment rails** | **x402 + rWallet + rFunds** | Multi-chain settlement (Base, Optimism, Arbitrum), community treasury pools |
|
||
| **Social graph & trust** | **rNetwork** | Reputation scoring, connection management, observable behavior history |
|
||
| **Audit trail** | **Automerge history** | Append-only, immutable change log — matches MEA's event immutability requirement |
|
||
| **Communication** | **rChat, rDocs, rFiles** | Intra-pod collaboration tools, ready to use |
|
||
| **Modular composition** | **RSpaceModule interface** | New MEA-specific modules plug directly into the existing system |
|
||
|
||
---
|
||
|
||
## Gaps to Build
|
||
|
||
| Gap | Priority | Effort | Description |
|
||
|---|---|---|---|
|
||
| **Exchange Gradient Engine** | High | 2–3 weeks | MEA's core economic innovation — pricing based on relational distance. `rate = min(1.00, 0.50 + 0.10 × counterparty_level)`. Requires graph-distance calculation across the pod hierarchy. |
|
||
| **Pod Mitosis Protocol** | High | 2–3 weeks | Growth through division, not expansion. When a pod exceeds ~12 members, it splits into two. Needs governance flow (vote to divide) + automated split logic. |
|
||
| **Pod Level Taxonomy & Caps** | Medium | 2–3 days | L0–L5 level types with enforced member caps (L0 = max 12, L1–L5 = max 8). Mostly configuration on existing Space primitives. |
|
||
| **Relationship Capacity** | Medium | 2–3 days | L0 pods maintain max 5 inter-pod relationships. Keeps the network intentionally sparse. Validation logic on rNetwork connections. |
|
||
| **Anti-Gaming** | Medium | 2–3 weeks | Transaction volume caps, burst detection, relationship cycling detection, Sybil resistance. |
|
||
| **Native Mobile Shell** | Low (MVP) | 4–6 weeks | Capacitor/React Native wrapper for true mobile-first UX (MEA's "Dharavi standard"). Not blocking for a web-based pilot. |
|
||
|
||
**Total new development: ~8–12 weeks** to full MEA protocol compliance.
|
||
First usable pilot possible after ~4–5 weeks (Phases 1–2).
|
||
|
||
---
|
||
|
||
## Strategic Assessment
|
||
|
||
rSpace isn't just "compatible" with MEA — the two systems share overlapping first principles:
|
||
|
||
- **Coherence over scale** — bounded groups, quality relationships
|
||
- **Sovereignty over convenience** — self-sovereign identity, local-first data
|
||
- **Protocol over policy** — defining valid interactions structurally, not legally
|
||
- **Emergence over control** — modules compose; behavior emerges from composition
|
||
|
||
### Recommended Approach
|
||
|
||
Build MEA as an **rSpace "flavor"** — a curated set of modules with MEA-specific
|
||
configuration and 2–3 new modules for the unique protocol elements (exchange gradient,
|
||
mitosis, integrity). This preserves rSpace's generality while giving MEA a concrete,
|
||
deployable implementation.
|
||
|
||
### Suggested Phasing
|
||
|
||
1. **Phase 1 — Configuration Layer** (1–2 weeks): Pod levels, member caps, relationship limits, lifecycle states
|
||
2. **Phase 2 — Exchange Gradient** (2–3 weeks): Distance calculation, rate engine, payment integration
|
||
3. **Phase 3 — Mitosis Protocol** (2–3 weeks): Threshold monitoring, governance-triggered division, automated split
|
||
4. **Phase 4 — Integrity** (2–3 weeks): Anti-gaming, rate limiting, anomaly detection
|
||
5. **Phase 5 — Mobile** (4–6 weeks, parallel): Native shell, offline optimizations, low-bandwidth UX
|
||
|
||
---
|
||
|
||
### Detailed Analysis Documents
|
||
|
||
- `mea-rspace-alignment.md` — Full capability mapping across all MEA concepts and rSpace modules
|
||
- `gap-analysis.md` — Detailed gap descriptions, suggested approaches, and phased implementation roadmap
|
||
|
||
---
|
||
|
||
*Analysis based on the full 104-page MEA document ("Mycelial Economics — A New Economics
|
||
for Humanity", 2026-03-29) and comprehensive review of rSpace-Online's codebase,
|
||
architecture, and 35-module ecosystem.*
|