Project Network Structure
"We can abandon hierarchy where it doesn't serve us" - Network of equals approach
Network of Independent Projects
This is a network of independent projects rather than a traditional hierarchy:
ClickForCharity.net
Charity & Social Platform - Focus: Charitable giving, social media automation, faucet lists - Status: Primary active platform - Domain: clickforcharity.net - Note: DirectSponsor evolved into ClickForCharity (documentation hosted at satoshihost.dev)
ROFLFaucet
Gaming & Entertainment Platform - Focus: Bitcoin faucet, gaming, token economy - Status: Standalone gaming platform - Relationship: Can work with ClickForCharity but operates independently - Domain: TBD
DirectSponsor.net
Documentation & Infrastructure Host - Focus: Development documentation, shared infrastructure - Status: Technical support entity for the network - Domain: directsponsor.net (hosts this documentation) - Evolution: Core charity functions moved to ClickForCharity - Future: DirectSponsor.org could become a project when network grows and there's actual need
Shared Technologies
Universal Coin System
Network-Wide Technology - Implementation: Each project implements their own interface - Governance: Collaborative development across network - Benefits: Cross-platform user experience
Infrastructure & Documentation
Hosted by DirectSponsor.net - Servers: ES7 (Production), Servarica 1 (Backup) - Documentation: This MkDocs system at satoshihost.dev - Rationale: "The docs had to go somewhere" - DirectSponsor hosts for the network - Status: Service provider, not hierarchical owner
Development Methodology
Network-Wide Standards - AI Collaboration: Shared workflow patterns - Documentation: Cross-project best practices - Deployment: Shared CI/CD infrastructure
Network Branding Approach
Documentation Hosting
- This Site: "DirectSponsor Developer Documentation"
- Purpose: Technical documentation for the project network
- Scope: Cross-project systems, infrastructure, development practices
- Location: satoshihost.dev (chosen as documentation host)
Project-Specific Branding
- ClickForCharity: All charity, social media, and user-facing features
- ROFLFaucet: All gaming, faucet, and entertainment features
- DirectSponsor: Infrastructure, documentation, technical systems
Network-Wide Features
- Universal Coin System: "Cross-project cryptocurrency earning"
- Shared Infrastructure: "Network infrastructure hosted by DirectSponsor"
- Development Practices: "Network development methodology"
Avoiding "Warp" References
- Never in public content: "Warp" is just internal folder structure
- Replace with: Specific project names or "project network"
- Technical docs: Can reference folder paths when necessary
Folder Structure Clarification
/home/andy/Documents/websites/Warp/ # ← Just a folder name, not a brand
├── projects/
│ ├── rofl/roflfaucet/ # ← ROFLFaucet project
│ ├── clickforcharity.net/ # ← ClickForCharity project
│ ├── directsponsor/ # ← DirectSponsor platform (less active)
│ ├── freehostingreviews/ # ← Hosting reviews project
│ └── warp-docs/ # ← Documentation system (DirectSponsor hosting)
Philosophy: Network Over Hierarchy
Inspired by the principle that "we can abandon hierarchy where it doesn't serve us," this structure treats projects as network peers rather than subsidiaries:
- ClickForCharity: Independent charity platform
- ROFLFaucet: Independent gaming platform
- DirectSponsor: Technical infrastructure provider
- Shared Tech: Collaborative development (Universal Coins, AI practices)
The documentation lives at DirectSponsor.net not because DirectSponsor "owns" everything, but because "the docs had to go somewhere" and DirectSponsor was positioned as the technical infrastructure provider.
Future Growth Philosophy
- Document vision early: Capture ideas while they're clear
- Implement when needed: Don't build without actual demand
- DirectSponsor.org: Could become a sponsorship platform when network has scale
- Organic expansion: Let success drive new project creation
Action Required: Update all documentation to reflect network structure rather than hierarchical ownership.
Last Updated: 2025-06-08 Status: Network structure clarified - ready for implementation