2.9 KiB
2.9 KiB
| id | title | status | assignee | created_date | labels | dependencies | priority |
|---|---|---|---|---|---|---|---|
| task-1 | Flesh out r*.online ecosystem architecture | To Do | 2025-12-12 23:41 | high |
Description
Follow up on the R-ECOSYSTEM-ARCHITECTURE.md document to develop detailed specifications for each module in the r-Ecosystem.
Reference document: /docs/R-ECOSYSTEM-ARCHITECTURE.md
Acceptance Criteria
- Each primary module has a detailed specification document
- Technical architecture diagrams created for cross-module data flow
- Possibility cones concept fully specified for rTime.space
- Domain redirect strategy documented and configured
- zk privacy layer requirements specified
- CRDT schema definitions drafted for each module
- User stories written for each module
- API surface area outlined for rStack.online
Subtasks
Module Specifications (create docs/modules/*.md for each)
- rSpace.online - Platform core spec
- rWallet.online - Treasury & economics spec
- rFunds.online - Campaigns & matching spec
- rMaps.online - Spatial intelligence spec
- rCalendar.online - Temporal coordination spec
- rTime.space - Spatio-temporal fusion spec (including possibility cones)
- rRules.online - Constitutional framework spec
- rVote.online - Decision engine spec
- rDemocracy.online - Deliberative space spec
- rWork.online - Contribution tracking spec
- rInbox.online - Secure messaging spec
- rData.online - Data layer spec
- rNetwork.online - Federation spec
- rStack.online - Developer platform spec
- rTube.online - Media hosting spec
Technical Foundation
- Define CRDT schema for unified state model
- Specify sync protocol (WebRTC + relay)
- Design zk circuit requirements for each privacy feature
- Plan local storage strategy (IndexedDB, OPFS)
Domain Management
- Verify all domain registrations
- Configure redirects (r-space → rspace, rcal → rcalendar, etc.)
- Set up placeholder landing pages for each domain
- Plan DNS/Cloudflare tunnel configuration
Integration Design
- Document cross-module reference patterns
- Design event system for inter-module communication
- Plan permission model inheritance across modules
- Specify data export/import formats
Notes
This task emerged from an ultrathink session exploring rSpace as a "digital collaboration space generator" where groups can use novel econ/gov/tech primitives with zk-enabled local-first data security.
Key insight: Keep rMaps and rCalendar separate, but fuse them in rTime.space for novel spatio-temporal coordination features like "possibility cones" - visualizing where/when group coordination is physically possible.
Related
- docs/R-ECOSYSTEM-ARCHITECTURE.md - Main architecture document
- convictionvoting.xyz, dokindthings.fund - Related concept domains